• Hello!

    I have two forums and on both of them I have the same error after the upgrade

    Fatal error: Call to undefined method stdClass::add_query_var() in ambnotes/wp-includes/taxonomy.php on line 316

    I’ve looked in the taxonomy.php file and here is not even 316 lines.

    How to fix it?

Viewing 15 replies - 1 through 15 (of 18 total)
  • Moderator t-p

    (@t-p)

    -Call to undefined function could mean that your upgrade probably did not succeed. Do a manual update via FTP instead: https://codex.www.ads-software.com/Updating_WordPress#Manual_Update

    -also review this sticky: https://www.ads-software.com/support/topic/troubleshooting-wordpress-31-master-list?replies=22

    Thread Starter aborisov

    (@aborisov)

    Tried to do manual update. Still getting same error message.

    https://core.trac.www.ads-software.com/browser/tags/3.1/wp-includes/taxonomy.php line 316 is
    $wp->add_query_var($args['query_var']);

    Change theme to default theme and deactivate all plugins..

    Thread Starter aborisov

    (@aborisov)

    Tried it too. Also, deleted /wp-admin and /wp-includes. Deactivated all of my plugins, activated default theme… Tried everything

    Still getting the same error.

    Moderator t-p

    (@t-p)

    have you discussed the issue with your hosting provider?

    I have two forums and on both of them I have the same error after the upgrade

    What forum plugin/s are you using?

    Thread Starter aborisov

    (@aborisov)

    For forum I’m using simple forum plugin. On my one wordpress site. But I think it is not really important because on another one I’m using bbpress. But what’s really interesting I’m getting the same error message on both wordpress sites.

    The error you mentioned was in all probability caused by a plugin or functions within custom theme, but more likely by a plugin.

    You mentioned you deactivated the plugins – via dashboard I presume? Deactivate plugins again, but this time rename the plugins folder to e.g. plugins-ex and then run Settings > Permalinks. Also, if you are on multisite and are using mu-plugins folder, rename that as well.

    Thread Starter aborisov

    (@aborisov)

    I don’t have multisites. Just two different wordpress blogs. They are separated.

    I’ll try to rename /plugins just don’t think it will make a differences. I’ll do it. Really sick now.

    I’ll try to rename /plugins just don’t think it will make a differences.

    It could make a difference because there are times when a recently deactived plugin can still cause problems. Same with renaming the themes folder in wp-content

    I have the same problem.

    I am getting this error message after using the WP automatic upgrade to 3.1:

    Fatal error: Call to undefined method stdClass::add_query_var() in …/wp-includes/taxonomy.php on line 316

    I checked that file, and it says:

    $wp->add_query_var($args[‘query_var’]);

    (as it should).

    I changed the plugin and theme folder names as directed above.
    I tried manually reinstalling WordPress. Problem persists.

    Moderator t-p

    (@t-p)

    Yes, t-p, thanks. I should have mentioned that.

    I can’t see anything relevant there for my issue. I am surprised that only two of us experienced this problem and complained about it (apparently), and that it persisted with a manual reinstall for both of us.

    I have a single WP install.

    Also, FWIW, I can’t change my theme, since I can’t login, but I did change the theme folder name, so it won’t be used.

    Ditto plugins, which were deactivated, but I changed the folder name anyway, trying to cover my bases.

    Moderator t-p

    (@t-p)

    check WP Track for any ticket,etc.

    -also, contact you hosting provider. Ask them if they have any other problem at their end, or they made any changes to your account, or if there are any limitations/restrictions, etc.

    Thanks, t-p. Will do.

    If anyone else has solved this problem, would love to hear.

    aborisov?
    I hope you did not give up.

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘Fatal error after upgrade’ is closed to new replies.