Note: This is probably not caused by wf-section beta. I just don´t know.Did anyone else got a server error 500 with this beta?
I installed this beta twice now and both times i got a problem afterwards with an internal server error and Xoops.
But one after another:
First try:Basic Information: Running XOOPS 2.0.6 with some modules including wf-section 1.01- uninstalled 1.01
- made sure all tables were dropped from the database
- beta 2.01 on this installation
- did some config settings in wf-section
- created a first section
... no response,
... pressed reload,
... seemed ok
... went back to main page ... boom server error 500
... same for site/admin.php ... user.php and so on
- restored the database from backup
- deleted wf-section module directory
- still not working
Second try:- deleted the website
- fresh install of XOOPS 2.0.6
- installed wf-section 2.01 beta
- did some configuring
- created several sections
- deleted and changed articles ... all fine
- just accessing my site again ... boom Internal server error 500
- checked the actual error log:
[size=x-small][Sun May 2 22:13:58 2004] [error] [client 217.9.28.44] Premature end of script headers: /usr/local/httpd/htdocs/789/726/sites/mtv/html/admin.php
[Sun May 2 22:14:10 2004] [error] [client 217.9.28.44] Premature end of script headers: /usr/local/httpd/htdocs/789/726/sites/mtv/html/index.php[/size]So i checked those files in the XOOPS root directory and found that a) the size has changed compared to the original XOOPS package
b) if i do a view file in smartFTP it will show the file in the standard windows editor. Those files now look compressed. Stripped of carriage returns and empty lines ...
(this is not so with another site (xoops2.0.3)
c) if i upload those files like index.php again from a fresh XOOPS 2.0.6 and view them they are shown normal with alle carriage returns and empty lines. And the site/pages is/are working again.
Well now i am left with those observations and additionally the following informations:- the site (xoops2.0.6) i was using wf-section beta on twice crashed on me (once full site with several modules, once only XOOPS with wf-section beta)
- another site based on XOOPS 2.0.3 didn´t show that (possible) problem with the files within the XOOPS root directory. But i didn´t try to run wf-section there
- problem on provider side: don´t think so. They have a good forum and usually there should be plenty users experiencing problems like this after such time
- server infos: Apache/1.3.29 (Unix) PHP/4.3.4 / MySQL 3.23.55
- the time stamp on the mentioned files like index.php, admin.php were still the times when i uploaded the fresh xoops. wf-section was uploaded one hour later so if it would have done something to the files it should be visible.
Anyone got a clue as to what to look for?