WordPress.org

1. shinkadesign
   Member
   Posted 4 years ago #

   HI guys, wondering if someone can help me out with a quick question.
   After upgrading to 2.1.1 (I think that's when it occurred since I don't get many comments), when someone posts a comment they get an Internal Server Error, though the comment is still posted.
   I checked my error log and got this (I don't know which is exactly culpable or if it's all of them):
   [Fri Feb 23 10:17:37 2007] [error] [client 66.142.214.149] PHP: Error parsing /home/840/etc/php.ini on line 18, referer: http://truthandthedevil.com/site-info/new-design/
   [Fri Feb 23 10:17:38 2007] [error] [client 66.142.214.149] Premature end of script headers: php4, referer: http://truthandthedevil.com/site-info/new-design/
   [Fri Feb 23 10:17:39 2007] [error] [client 66.142.214.149] PHP: Error parsing /home/840/etc/php.ini on line 18

   Thanks for any help you could provide.

2. shinkadesign
   Member
   Posted 4 years ago #

   Anybody have any ideas? I'd really like to get this resolved.
   Thanks.

3. shinkadesign
   Member
   Posted 4 years ago #

   I've tried a few changes that were posted on here previously (some tweaking with the php.ini file), but none seemed to work.
   Is this something I should take up with my server providers directly? Or is there something I can do on my end?

4. shinkadesign
   Member
   Posted 4 years ago #

   Please? I'd really like to get my site back to working order sometime soon. If no one on here is willing to help, can someone at least direct me to another site with information or people who are available?
   Thanks a lot.

5. Chris_K
   Member
   Posted 4 years ago #

   Not sure I see this as a WP issue.

   PHP: Error parsing /home/840/etc/php.ini on line 18,

   What's at line 18 of that file?

6. shinkadesign
   Member
   Posted 4 years ago #

   That's part of the weird part. Line 18 seems to be:
   # For performance reasons, (mt) does not load all of the modules that are available
   Unless the php.ini file doesn't recognize spaces, in that case it would be:
   

   session.save_path=/home/840/data/tmp

   Thanks for replying.

7. Chris_K
   Member
   Posted 4 years ago #

   hrmm, yeah. A php forum may get you further.

   You could just delete the commented "for performance reasons" and see if anything changes... (I think you need to restart the web server on php.ini changes?)

   ... or you could make sure that the web server process can write to the session.save_path. The error doesn't seem to lean that way though.

   Yep, I'm of no value here. :-\

8. shinkadesign
   Member
   Posted 4 years ago #

   Okay, I'll try a few things out. Thanks a lot for your input.

9. shinkadesign
   Member
   Posted 4 years ago #

   It ended up being a plug-in. Thought I'd close up the topic.

Topic Closed

This topic has been closed to new replies.