Morning all,
First off - I'm not really expecting a useful response here because I wouldn't believe me either
Config is as follows:
Slackware Linux
Lighttpd 1.4.13
PHP 5.2.3 running via FastCGI
MySQL 5.0.27
eAccelerator 0.9.5.1
vBulletin 3.6.4 (yes, I know )
Yesterday afternoon, I upgraded PHP from 5.2.0 and eAccelerator from 0.9.5.
According to my users, the Archive built into vBulletin was working beforehand. It does not work now - it errors with: "No input file specified".
In the AdminCP, it says that the SE-friendly Archive only works with Apache HTTPd and PHP compiled as a module. We have not had that setup for at least 9 months and I know that the Archive has worked in that time.
I'm not in the habit of removing modules from PHP etc - I tend to carry the same configuration forward (via arguments to ./configure) wherever possible. As far as I can tell, nothing in PHP's config has changed.
I have seen it mentioned on here that the Archive uses certain features unique to Apache. This may have been the intention but it evidently has worked in Lighttpd, but it does not work anymore. Does anyone have any suggestions?
HB
First off - I'm not really expecting a useful response here because I wouldn't believe me either
Config is as follows:
Slackware Linux
Lighttpd 1.4.13
PHP 5.2.3 running via FastCGI
MySQL 5.0.27
eAccelerator 0.9.5.1
vBulletin 3.6.4 (yes, I know )
Yesterday afternoon, I upgraded PHP from 5.2.0 and eAccelerator from 0.9.5.
According to my users, the Archive built into vBulletin was working beforehand. It does not work now - it errors with: "No input file specified".
In the AdminCP, it says that the SE-friendly Archive only works with Apache HTTPd and PHP compiled as a module. We have not had that setup for at least 9 months and I know that the Archive has worked in that time.
I'm not in the habit of removing modules from PHP etc - I tend to carry the same configuration forward (via arguments to ./configure) wherever possible. As far as I can tell, nothing in PHP's config has changed.
I have seen it mentioned on here that the Archive uses certain features unique to Apache. This may have been the intention but it evidently has worked in Lighttpd, but it does not work anymore. Does anyone have any suggestions?
HB
Comment