Support

NiteWave · #11 10-10-2010, 07:08 PM

no problem of the permission. it's strange of your issue. Can you PM me the access to your server.

lugus · #12 10-10-2010, 08:30 PM

Message sent.

lugus · #13 10-10-2010, 10:53 PM

Problem solved. Thanks for the incredible support. Look forward to 4.1 in the future.

IrPr · #14 10-12-2010, 01:44 PM

Would you please let me know whats the solution for PHP compile issue ?

lugus · #15 10-12-2010, 05:24 PM

Unfortunately there was an issue with the update that the Litespeed team repaired for me. In the past when I had a similar error using apache it was down to there being insufficient memory allocated to php.

NiteWave · #16 10-12-2010, 06:24 PM

the issue was introduced by 4.0.17 new feature:mod_action support. its PHP Content-Type is "handler/fcgid-script". the new 4.0.17 build ignore "fcgid-script" and fixed the problem.

lugus,
can you give more info about your current problem? you can post here or through PM.

lugus · #17 10-12-2010, 07:25 PM

Sorry, I did not mean to imply I had an issue now. I should have said, the update originally caused a problem but was cured after work by the Litespeed team.

Jos · #18 10-24-2010, 04:16 AM

Quote:

Originally Posted by lugus

Upgraded using cp to 4.0.17. When I went to login to my Wordpress blog it tried to download the file login.php rather than run it. Same with other admin php files. When I went back to 4.0.16 the problem went away.

Any ideas?

PHP 5.3.3 on Centos 5.x

To experience wordpress "WSOD" (white screen of death) when upgrading isn't funny and very timeconsuming. You'll get no clues at all, nothing in the logs. Just a white screen telling nothing.

I did an uprade to lsws 4.0.17 and instantly it killed my blog. Now it is up and running again, but it took a while before finding out what it was which caused the downtime. A bug, hacking or something else?

In my case the lsws upgrade in cooperation with the debian server did corrupt the mysql database by giving it a mix of UTF8 and latin1 encodings which resulted in "funny characters". It wasn't easy to restore the database and reinstall everything. Now lsws 4.0.14 is installed together with php 5.2.13 and it seems to work very well.

Finally after searching the net I learned the path how to get out of the mess. Valuable search terms are: "Turning MySQL data in latin1 to utf8 utf-8" (I cannot link to the actual site due to this is my 1st post in this forum).