Search results

  1. L

    [Resolved] 4.0.16-> 4.0.17 Broke my wordpress blog

    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.
  2. L

    [Resolved] 4.0.16-> 4.0.17 Broke my wordpress blog

    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.
  3. L

    [Resolved] 4.0.16-> 4.0.17 Broke my wordpress blog

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

    [Resolved] 4.0.16-> 4.0.17 Broke my wordpress blog

    Message sent.
  5. L

    [Resolved] 4.0.16-> 4.0.17 Broke my wordpress blog

    Produces: drwx------ 3 lsadm lsadm 4096 Oct 10 23:05 /usr/local/lsws/phpbuild/
  6. L

    [Resolved] 4.0.16-> 4.0.17 Broke my wordpress blog

    Also I have just found if I try and compile php under 4.0.17 I receive: Fail to generate build script, please try to manually fix the error first. Failed to create manual install script: /usr/local/lsws/phpbuild/buildphp_manual_run.sh
  7. L

    [Resolved] 4.0.16-> 4.0.17 Broke my wordpress blog

    I do not have any opcode cache compiled at the moment while I experiment. I will when this server goes into full use. I definitely do not want to add it now until I sort out why patch 4.0.17 is breaking the php.
  8. L

    [Resolved] 4.0.16-> 4.0.17 Broke my wordpress blog

    I would if I thought it could help but I do not have APC compiled in my php at all and 4.0.16 works fine without it. Are you saying I have to have it now for 4.0.17?
  9. L

    [Resolved] 4.0.16-> 4.0.17 Broke my wordpress blog

    Version 3 of Wordpress. Is there a chance I need to rebuild php after the upgrade? Have you tinkered with php memory or anything along those lines?
  10. L

    [Resolved] 4.0.16-> 4.0.17 Broke my wordpress blog

    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
Top