[resolved] Upgrade to 3.0.4 causes fatal error (8 posts)

  1. gideonstrumpet
    Posted 5 years ago #

    Hi folks, I'm at a bit of a loss as to how to resolve this situation. Following Matt's email and the WPAU notification, I started the upgrade to 3.0.4. Made it to the very last step where you check in another tab whether the database needs updating. It did not. Then I clicked on "click here for the final step", etc. Pretty routine, happens always.

    Then I get this:

    Fatal error: Call to a member function get_feed_permastruct() on a non-object in /home1/apublic1/public_html/wp-includes/link-template.php on line 429

    The site worked fine on 3.0.3 up until I was completing the upgrade. No new plugins installed between the upgrade commencing and the fatal error. Usually I'd try and uninstall the last installed plugin or go through and deactivate them one by one, but without any admin access, I don't want to start willy-nilly FTP deleting plugins that I use.

    Any suggestions?

    URL, if needed: Here

  2. gideonstrumpet
    Posted 5 years ago #

    Line 429 states:

    $permalink = $wp_rewrite->get_feed_permastruct();

  3. I don't want to start willy-nilly FTP deleting plugins that I use.

    You may not have a choice and it may be your theme. But before that, give these a try.

    1. Backup your files and database and get ready to restore both as a just in case.


    2. Download the WordPress 3.0.4 files and upload the files to your webserver.

    http://wordpress.org/wordpress-3.0.4.zip or http://wordpress.org/wordpress-3.0.4.tar.gz

    3. Perform a manual upgrade.


    This advice is just to see if your upgrade got munged.

    Or after you backup the whole works you can rename wp-content/plugins to wp-content/plugins-old and see if your blog comes up. If it does come up then put your plugins back one at a time and see which is the offending plugin.

    If it's your theme, try switching to Twenty Ten and see if that does it.

  4. gideonstrumpet
    Posted 5 years ago #

    Thanks for your help! While you were typing that, I started renaming all the plugins one by one, figuring that's a way of "deactivating" them. Turns out, it was the podpress plugin (yet again). Back to normal now. Thanks a bunch, I'm going to save your reply in case this comes up again in the future.

  5. gideonstrumpet
    Posted 5 years ago #

    Although, now I apparently do not have sufficient permissions to reactivate plugins. Sigh. What does this mean? Does anyone know how to fix it?

    Edit: Nevermind, please ignore. Seems to be a plugin related problem, not a WP problem. Can reactive some, if not most. Sorry for the stupid question.

  6. ntm
    Posted 5 years ago #

    It is most likely a problem of podPress (although it occurred after a WP upgrade). You may follow and participate in this thread http://wordpress.org/support/topic/plugin-podpress-884-upgrade-causes-white-screen-in-multi-site

  7. dael3
    Posted 5 years ago #

    so you renamed your plug-ins back to original?

    I had same deal and renamed podpress and upgraded it which created the new podpress folder that works fine. and the upgrade is ok too

  8. gideonstrumpet
    Posted 5 years ago #

    Yes, I renamed them back to what they were after I got the site to load.

Topic Closed

This topic has been closed to new replies.

About this Topic