Corrupted installation or other problem?

Steerpike · 2006-01-03 23:07:56

Hi, I’m new to TextPattern, having been pointed this way by a fine fellow over on the nucleus forums.

I’ve just downloaded the latest package, and installed on my hosted web server in a standard fashion. I made one test post, and got what I consider to be strange results; the results suggest a problem with css (just my noob guess) but I checked all the uploaded files and everything seems fine. I spent several hours troubleshooting, but can’t see anything wrong. All I’d like at this point is a quick confirmation that this is/is not what I should be seeing.

Here is a link to the new site / post …

http://www.sequoiahills.com/textpattern/

I was expecting a much more ‘formatted’ look. I’ve played around with the default style, and it has no effect on the page – I tried changing background color, for example, but the background remains pure white. So … I’m probably missing something very obvious here!

Thanks for any assistance you can offer!

zem · 2006-01-03 23:19:13

http://www.sequoiahills.com/textpattern/textpattern/css.php?s=default

Warning: main(): Unable to access ../textpattern/textpattern/publish.php in /home/virtual/site174/fst/var/www/html/textpattern/textpattern/css.php on line 19 
Warning: main(../textpattern/textpattern/publish.php): failed to open stream: No such file or directory in /home/virtual/site174/fst/var/www/html/textpattern/textpattern/css.php on line 19

..etc. Looks like you’ve used a relative path for your txpath setting in config.php. It has to be absolute (probably /home/virtual/site174/fst/var/www/html/textpattern/textpattern/ in your case).

Steerpike · 2006-01-04 00:02:39

Well thank you so much – you are (of course!) entirely correct! Fixed the problem and it looks …;)… just a tad better!

I recall now having an initial problem right after the upload, ultimately traced to a premature termination of the ftp session (and thus missing files). But part of my initial troubleshooting suggested a problem with the very path you mention, and I changed it from absolute to relative. When I later discovered that some files did not make it to the server, I did not change this path back from relative to absolute … and things ‘seemed’ to work with the relative path, so I did not think to change it back – my bad.

Regarding this path – as you can see, it’s a very long and cryptic path, on account of my site being on a hosted server. I was very uncomfortable using this path since it looks like something highly likely to change, if my web host ever decides to relocate my site (which I imagine they do from time to time). Is there ‘any’ way to avoid using the entire path? Here’s the path again, for reference. I’ve never had to enter this path ever before for any other application …

$txpcfg[‘txpath’] = ‘/home/virtual/site174/fst/var/www/html/textpattern/textpattern’;

I’ve always treated the path from ‘/var/www/….’ as being the absolute path in the past. I guess I could just try it and see … but once bitten twice shy!

Thanks again …

zem · 2006-01-04 00:37:32

This is what we’re using in the 4.1 branch:

$txpcfg['txpath'] = dirname(__FILE__);

Textpattern CMS

Textpattern CMS support forum

#1 2006-01-03 23:07:56

Corrupted installation or other problem?

#2 2006-01-03 23:19:13

Re: Corrupted installation or other problem?

#3 2006-01-04 00:02:39

Re: Corrupted installation or other problem?

#4 2006-01-04 00:37:32

Re: Corrupted installation or other problem?

Board footer