Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • h2ocello

    (@h2ocello)

    @bgswm1

    That sounds like a different error than the posts in this thread. The sole error I get that this thread references is ‘500 Internal Server Error’. Regardless, have you tried unpublishing the ‘culprit’ post by changing it to Draft? Tried to remove tags for the article?

    I read in another of your postings you use GoDaddy. I have GoDaddy too, although I haven’t had the 500 Error problem occur now for several weeks. I’m running WordPress 2.1.2.

    @vkaryl

    My PHP version is actually older than all you mentioned, 4.3.11.

    h2ocello

    (@h2ocello)

    @navigadget

    Regarding your host’s comment:

    Please check your PHP encoding and ensure that all of your database calls fully close to ensure that they are not being left open, which can cause an increase in these errors.

    WordPress does not explicitly close database connections. It relies on PHP to automatically close them at the end of script execution.
    See this: WordPress Support > Closing db connections

    On PHP.net, on their page about mysql_close() they discuss the issue of closing databases explicitly. I am not an expert, but it appears it’s typically ‘bad form’ to explicitly close db connections. The database will close as soon as its script finishes. After reading that a few weeks ago on PHP.net (when I was researching the very same thing) I decided to remove all the mysql_close() commands I’d written into some PHP scripts I run (not my WordPress blog–it was for something else) and I have seen an improvement in speed on those scripts since then. And no 500 internal server errors on those sites either, not that I’d ever had them before.
    See this: PHP.NET mysql_close page

    I posted my 500 internal server error issues in this topic a few weeks ago. I’ve had no issues at all since updating to 2.1.2, knock on wood. I’m not sure if that has anything to do with not seeing the error anymore. I do still watch for it.
    My 500 internal sever error problems and related discussion.

    @tuntis

    I’m having a (possibly) similar issue:
    – shared Linux
    – WP 2.1
    – intermittent 500 Internal Server Errors
    – happening in various themes (I use MistyLook)

    My issues that are not similar:
    – usually only occurring on home page

    My issues that may or may not be like yours:
    – error occurs the same in FF and IE (have not tested other browsers)

    If you change your Home Page to something other than most recent posts, do you still get the error? When I do that, my error immediately & completely disappears. Only thing I’ve been able to figure out so far, is the error seems to be tied to publishing posts to Categories (Tags) – either certain ones or ones that are nested 3-deep (Example nested hierarchy: Food > Lunch > Sandwiches).

    When I
    (1) change my newest (“offending”) post to draft AND
    (2) make my Home Page show most recent posts again
    the Home page is fixed.

    Also when I
    (1) change categories for my new post (like only post to categories/tags that are 1-category deep) AND
    (2) republish my new post AND
    (3) make my Home Page show most recent posts the Home Page is fixed.

    Not sure if I’m on the right track or not, but for now this seems to be the fix for me. I’m keeping track of my intermittent 500 Internal Server Errors and the fixes here.

    Rooboy, can you please send me the zip of the plugin too? melissa@yaderhey.com Thank you!

Viewing 4 replies - 1 through 4 (of 4 total)