• Error log says this:

    Sun Apr 9 13:04:41 2006] [error] [client 69.109.59.81] Premature end of script headers: /home/(my folder)/public_html/index.php

    All other errors are page not found errors.

    Index.php says this:

    /* Short and sweet */
    define(‘WP_USE_THEMES’, true);
    require(‘./wp-blog-header.php’);
    ?>

    What the heck is going on? Why am I getting a server error on that page?

    Interestingly, it’s only the main index page that I have this problem on. I can view post and category pages just fine.

    Thanks!!!

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter doubledubs

    (@doubledubs)

    OK – I figured it out. The problem was not a server error as I correctly assumed (the error logs made no sense).

    The problem was with the tagging of my footnotes plug-in that I still love. I left an open footnote tag that was improperly formatted (it’s supposed to be a double open paren to indicate the beginning of a new footnote – I put a single open paren). This apparrently caused both the individual post page and the index.php that it was sitting in to fail.

    Often you get that if the directory is chmod 777 instead of 775…

    Thread Starter doubledubs

    (@doubledubs)

    Thanks for the reply. I don’t get many replies here (I usually figure it out myself after 2 days of pure anguish) which is why I post my own solutions.

    My plug-in directory is set at 755 and the footnote plugin is also at 755.

    My intention is just to avoid mistagging my footnotes from here on out. ??

    This bug in Footnotes will be squashed in the next release.

    Cheers,
    S.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘500 Internal Server Error’ is closed to new replies.