The MU forums have moved to WordPress.org

Error page after user deleted her blog (13 posts)

  1. charlie_hun
    Member
    Posted 14 years ago #

    When user deleted her blog, and other people show her blogs, WordPress MU serving a blank page.

    How to maketo server Wordpress an error page (eg.: This blog is deleted)

  2. SteveAtty
    Member
    Posted 14 years ago #

    Blank page means PHP error - look in your php error logs.

    Modlook added for second post for the sig file.

  3. charlie_hun
    Member
    Posted 14 years ago #

    I dont see any php error in the log files.

  4. SteveAtty
    Member
    Posted 14 years ago #

    If its a totally blank page then its a php error, If you look at the source of the page in the browser is there anything there at all?

  5. charlie_hun
    Member
    Posted 14 years ago #

    I enabled WordPress debug mode:

    in wp-config.php
    define('WP_DEBUG', true);

    But in nothing error display or loggin in the error log.

    ----------------

    I created a WP_CONTENT_DIR . '/blog-deleted.php' file, and this works.

  6. SteveAtty
    Member
    Posted 14 years ago #

    you need to enable error logging in your php.ini file to control what you are logging and where you are logging to

  7. charlie_hun
    Member
    Posted 14 years ago #

    I got the error: because Apache says content-lenght: 0, the front-end lighty serve only the http header.

  8. SteveAtty
    Member
    Posted 14 years ago #

    So is php error reporting enabled, and set to report to a file, in your php.ini file?

  9. charlie_hun
    Member
    Posted 14 years ago #

    Steve: This is not a php error, this is an Apache (?) bug and/or lighty bug and incompatibly.

    Lighty not waiting and serve the html content, only the http header, because the apache says content-lengh zero in http header.

  10. SteveAtty
    Member
    Posted 14 years ago #

    So your running lighttpd alongside Apache to serve static content?

  11. charlie_hun
    Member
    Posted 14 years ago #

    client -> lighty ->

    if static content (files.domain.tld, OR *.css, *.js, any picture, etc) lighty serve to the client

    if dynamic content -> apache ; apache generate the content -> lighty -> client

    so, for dynamic content, lighty is a reverse proxy (but, lighty don't cache the content)

  12. SteveAtty
    Member
    Posted 14 years ago #

    So its likely that this is a lightly/Apache issue rather than WPMU?

  13. charlie_hun
    Member
    Posted 14 years ago #

    Yes.

About this Topic

  • Started 14 years ago by charlie_hun
  • Latest reply from charlie_hun