WordPress.org

Ready to get started?Download WordPress

Forums

Pages Messed up, Internal Server Errors and other fun (7 posts)

  1. j4ckplu9
    Member
    Posted 3 years ago #

    OK, so I have WP2.0.5 running on godaddy servers.

    Client called to say their site was messed up.

    Indeed... some [well, most] pages are broken and a visit to the admin makes grim viewing.

    the page viewer can't display [most] of the pages and when you try to create a page from scratch, it fails to load any of the page beyond "pageparent" dropdown...

    also:
    - theme page empty & the theme editor 500s
    - plugin page empty & the plugin editor 500s

    I'm a bit in the dark... any ideas appreciated.

  2. James
    Happiness Engineer
    Posted 3 years ago #

    Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for anything useful. If you don't have access to your server error log, ask your hosting provider to look for you.

    Once you get those take care of, you should really consider upgrading. WP 2.0.5 is full of several publicly know security vulnerabilities. In fact, one of those vulnerabilities may be the source of your sudden problems.

  3. j4ckplu9
    Member
    Posted 3 years ago #

    Hmmm... if I upgrade the site from 2.0.5 to 3, is there something I need to do to update my custom theme and the sql itself?

    Feel this is going to be more difficult than I'd anticipated :(

  4. James
    Happiness Engineer
    Posted 3 years ago #

    You'll need at least PHP 4.3 and MySQL 4.1.2. Your custom theme should work. If it doesn't we can help you resolve any theme-specific problems after the upgrade.

    Since you're so far behind, the upgrade path will take some time, but the security is worth it.

    The "semi-official" WordPress major upgrade path:

    1. Backup the files and the database.

    2. Download WordPress 2.2.

    3. Do a manual upgrade to WordPress 2.2.

    4. Repeat step 1, but don't replace the previous backup (keep both on hand).

    5. Download WordPress 2.4.

    6. Do a manual upgrade to WordPress 2.4.

    7. Repeat step 1, but don't replace the previous backup (keep both on hand).

    8. Download WordPress 2.6.

    9. Do a manual upgrade to WordPress 2.6.

    10. Repeat step 1, but don't replace the previous backup (keep both on hand).

    11. Download WordPress 2.8.

    12. Do a manual upgrade to WordPress 2.8.

    13. Repeat step 1, but don't replace the previous backup (keep both on hand).

    14. Use WP's automated upgrade to system to upgrade to 3.0.

  5. j4ckplu9
    Member
    Posted 3 years ago #

    hmmm... i don't have that kind of access to the server on godaddy.

    looks like this is going to be some uphill redev - unless i can isolate why it broke :/
    thanks though - will see if I can get hold of the logs to see why certain elements are just not displaying right

  6. j4ckplu9
    Member
    Posted 3 years ago #

    Hi

    I had a look at the source of the page creator which was breaking and the HTML ended after the pageparent fieldset loads. so i took out the next piece of code [below] loading the pagetemplate and the page loads fine... had no effect on the viewing existing page which gives the internal server error. Might tht shed any light on the problem?

    <?php if ( 0 != count( get_page_templates() ) ) { ?>
    <fieldset id="pagetemplate" class="dbx-box">
    <h3 class="dbx-handle"><?php _e('Page Template:') ?></h3>
    <div class="dbx-content"><p><select name="page_template">
    <option value='default'><?php _e('Default Template'); ?></option>
    <?php page_template_dropdown($post->page_template); ?>
    </select></p>
    </div>
    </fieldset>
    <?php } ?>

  7. j4ckplu9
    Member
    Posted 3 years ago #

    Some pages display, some do not...

    more investigation shows that the consistent element is HTML in page_content - if I go into phpmyadmin and remove HTML from that field, the page displays... OMG, help! hehe

Topic Closed

This topic has been closed to new replies.

About this Topic