Hi! I downloaded the 1.0.1 to do a clean install. At first the installer worked correctly, giving me the "fatal errors" screen instructing me to fix the permissions on certain files. (The zip file didn't include the /archives folder, so I created it.) With the permissions fixed, though, I just get "500 server error" when I try to go to index.php. There is no .htaccess file so I can't delete it.
Can anybody help? Thanks!
500 Server Error before doing anything
-
garvinhicking
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Hi!
Can you look up your Apache and PHP error logs to see why you get a 500 error? It can depend on your server setup, maybe it does not allow any PHP header() calls; you could edit your index.php to temporarily remove all header() calls there (or put a "#" in front of it)?
Best regards,
Garvin
Can you look up your Apache and PHP error logs to see why you get a 500 error? It can depend on your server setup, maybe it does not allow any PHP header() calls; you could edit your index.php to temporarily remove all header() calls there (or put a "#" in front of it)?
Best regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
the only log file I've been able to find is useless, it just says something like:
Thanks!
Can you point me to where I might find a decent log file? This is a shitty shared server so it might be that the reason I can't find it is because it doesn't keep logs / I don't have access to them.165.82.80.42 - - [11/Oct/2006:11:13:29 +0800] "GET /XXX/serendipity/ HTTP/1.1" 500 1005 "-" "Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.3) Gecko/20060427 Camino/1.0.1"
Thanks!
-
garvinhicking
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Hi!
Sadly that snippet comes from the ACCESS log, not an error log. Could you ask your web provider for the error log? If there's no .htaccess file, there must be some other PHP error that is specific to your hosting provider...
HTH,
Garvin
Sadly that snippet comes from the ACCESS log, not an error log. Could you ask your web provider for the error log? If there's no .htaccess file, there must be some other PHP error that is specific to your hosting provider...
HTH,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
Your server is configured to not allow certain directives in the .htaccess. DirectoryIndex is one of those directives. We use it to redirect URLs that point to the Serendipity directory so they point at our index.php.
Naturally, when you deleted the .htaccess, you deleted the DirectoryIndex inside it, so normal access was restored. And Serendipity works just fine that way (although URLs requesting your directory will return whatever your server has configured, and you aren't allowed to change it).
If you've got a copy of the .htaccess elsewhere (and I know you do; you seem like somebody who would've backed it up before deleting it
), you can just take out the DirectoryIndex line and see if there's anything else your server prohibits in there.
We also use the .htaccess to redirect 'pretty' URLs: the ones without "index.php?whatever" in them. That looks better, and the search engines understand them better, too.
Naturally, when you deleted the .htaccess, you deleted the DirectoryIndex inside it, so normal access was restored. And Serendipity works just fine that way (although URLs requesting your directory will return whatever your server has configured, and you aren't allowed to change it).
If you've got a copy of the .htaccess elsewhere (and I know you do; you seem like somebody who would've backed it up before deleting it
We also use the .htaccess to redirect 'pretty' URLs: the ones without "index.php?whatever" in them. That looks better, and the search engines understand them better, too.