Problem With Archive For SMF

Hello,

I got around to installing the archive mode for SMF 1.0.7 today, but I'm having a little trouble.  I'm getting a 500 server error when I visit domain.com/forum/archive.php

I read the README, but it doesn't appear that there are any special requirements that I'm lacking. 

Any ideas?


I tried chmodding the archive.php to 777, 666, and whatever the default setting was but that doesn't to have helped.

Thanks,
Brandon Drury

[Join us @ facebook]

That's very strange.

Can you please tell me a little about your server environmet? (operating system, php version)

I seam to have a gift for finding the exceptionaly strange errors. 


Here's my php info.

http://www.recordingreview.com/test.php


Brandon

[Join us @ facebook]

It appears that you have a development version of php. Maybe this is the problem (500 errors are not a regular type of crash in a php application)

I will try to find out what's going on, but 99% the problem is in the php you have installed in the server(we have tested the script with several php/apache/operating system versions).

Okay, I'll send an email to my host and see what they say.

Thanks,
Brandon

PROBLEM SOLVED!!!!

It was a chmod error.  Apparently, I didn't chmod all the files.  Either way, this is one truely great mod.  If the search engine spiders will snag it (which I don't see why not, this could be worth some decent cash!!).  I may owe you a beer (or whatever the online equivalent to that is).

Here's what my support guy said.  Maybe it'll help you understand what happened in my case. 

Thanks a mega ton,
Brandon Drury


Hello,

The archive.php and archive.css files were having world writable permissions (666). Such permissions are not allowed on our servers. We changed them to 755 and now the http://www.recordingreview.com/forum/archive.php URL opens fine for us.

Our servers are running SuExec, which is the most secure environment for a shared hosting server. The scripts are run with the user of their owner (your CP user) and not with the user of the web server (apache). Thus, if a script has to be able to write to a file/directory - world-writable permissions are no longer needed. Actually, such permissions are considered as insecure and files with world-writable permissions will not be executed - the result will be "500 Server Error".
If your installation manual says that you should set world-writable permissions to some files/directories, you need to set permissions 775 or 755 instead - and your script will work properly. It is just not presumed that the server may be running a CGI wrapper (such as Suexec).

Please, let us know if you need any additional assistance.

Best Regards,
Support

[Join us @ facebook]

That's great. I am glad that it worked

I guess the problem was that evil permissions (666)

[Guest]

[62.872]

adsense, hobbit, Yahoo crawler, Msnbot