PDA

View Full Version : Upgrading problem


delevinson
07-12-2005, 04:07 PM
I upgraded to RC4, but when I ran the install I got the messages
P Version >= 4.1 (5.0.4)
Server API (cgi-fcgi)
GD Support (for visual confirmations) (2.0)
Session Save Path writable? (/tmp)
MSSQL Server Support Not available.
MySQL Support OK
PostgreSQL Support Not available.
./include/config.php writable? OK
./temp writable? OK
./temp/templates writable? OK

I saw that MSSQL and PostgreSQL can be ignored, but the next button just returns me to this screen. What should I do?

David
07-12-2005, 04:19 PM
Content visible to registered users only.

Are you running PHP 5?

Can we see your url?

delevinson
07-12-2005, 04:40 PM
Here's my php config:
http://www.lib.lfc.edu/david/test.php

and the directory site:
http://www.lib.lfc.edu/david/phpLinkDirectory-2.0.0rc4/install/index.php

David
07-12-2005, 05:05 PM
That is definitely a different problem that we have not seen before.
One thing that has solved a lot of problems is to ask you to please try uploading all the files again. Sometimes one gets missed for one reason or another. Try that first, and if it is still not working, I may request you send me access to your server if possible, so we can investigate further.
Thanks,
David

delevinson
07-13-2005, 05:07 PM
I tried uploading the files again and got the same problem. I'd be glad to let you look at my system if it'd help.

Also, I have a mod suggestion: I'd like to list a link in multiple categories. Thanks!
David

springdot
07-13-2005, 05:36 PM
I actually got this problem when installing earlier, but when I looked closely at the first screen I was returned to, there was more writing above everything else saying something like

"smarty.class.php not registered"

There was more to it than that, but that was the basic feeling of the message. I tried uploading the files again and had the same problem.

At the time, I was using the server IP address, followed by /~xxxxx to access a particular user account on the server, HOWEVER...

as soon as I started using the actual domain name pointing at that account, (ie, www.xxxxx .com) there was no problem.

I don't suppose something similar could be causing your problems?

Cheers
James