Deprecated and Strict Standards errors on top of blog

  • I’m running an old version of WordPress, 2.2.1. Yes, I know, but if it ain’t broke, why fit it?

    Well, it’s finally broke.

    The following errors are appearing on the header of my site:

    Deprecated: Assigning the return value of new by reference is deprecated in /home/clackam/public_html/blog/wp-includes/cache.php on line 36

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /home/clackam/public_html/blog/wp-includes/cache.php on line 389

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl($output) in /home/clackam/public_html/blog/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl($output) in /home/clackam/public_html/blog/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el($output) in /home/clackam/public_html/blog/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el($output) in /home/clackam/public_html/blog/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el($output) in /home/clackam/public_html/blog/wp-includes/classes.php on line 556

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl($output) in /home/clackam/public_html/blog/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl($output) in /home/clackam/public_html/blog/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el($output) in /home/clackam/public_html/blog/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el($output) in /home/clackam/public_html/blog/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el($output) in /home/clackam/public_html/blog/wp-includes/classes.php on line 678

Deprecated: Assigning the return value of new by reference is deprecated in /home/clackam/public_html/blog/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /home/clackam/public_html/blog/wp-includes/theme.php on line 507

    I also can’t log in to my admin area.

    I’ve tried renaming my plugins directory — no luck.
    I’ve tried renaming my theme and reverting to default — no luck.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator Marius L. J.

    (@clorith)

    I’m going to just start right off with “dude, update your site.”

    These seem to be errors generated by PHP, most likely your host has updated their PHP version and that extremely old version of WordPress unfortunately doesn’t work too well with the version they now run.

    I’d also like to point out that by design we don’t normally support such old versions because of all the potential problems that have been solved in the following releases (the current latest stable release as of this post is 4.1).

    These errors are showing up because there are classes defined that extend built-in WordPress classes. The extender classes need to have exactly the same parameters defined. For example, with the start_el error, the extender function should have these parameters (as of WordPress v4.2.2 – the parameters may be different for the version you’re using.)

    function start_el( &$output, $page, $depth = 0, $args = array(), $current_page = 0 ) {

    This article references a similar issue:
    https://stackoverflow.com/questions/9734422/errors-when-trying-to-integrate-wordpress-on-my-existing-website

    As Marius suggested, updating your site to the latest version of WordPress is always recommended. Running an old version opens you up to potential security vulnerabilities.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Deprecated and Strict Standards errors on top of blog’ is closed to new replies.