• Resolved Michael

    (@nikonratm)


    After updating one of my two multi-site installs was failing with the error:

    PHP Fatal error: Call to a member function add_cap() on a non-object in /…/wp-content/plugins/all-in-one-seo-pack/aioseop_class.php on line 1697

    This was simple enough for me to fix with:
    if (is_object($role)) $role->add_cap( 'aiosp_manage_seo' );

    I’m not sure I get why the line above $role = get_role( 'administrator' ); was returning null in the first place. Looking in the database both sites have the role defined under wp_options with the key ‘***_wp_user_roles’.

    Any thoughts?

    https://wordpress.org/plugins/all-in-one-seo-pack/

Viewing 11 replies - 1 through 11 (of 11 total)
  • Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    I’m not sure off the top of my head. I’m looking into it now.

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    Michael,

    So far we’ve been unable to reproduce.

    Did you see this immediately after the upgrade, or did it appear to successfully upgrade, then later after you clicked around you got the message?

    Thread Starter Michael

    (@nikonratm)

    It was immediate. The first of the two sites on my install was working fine but the second site wouldn’t load at all. I tried deactivating and re-activating but got the same result.

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    We’ll fix it in a minor release this week… The obvious thing to do is just is_object but we’re still investigating why it’s an issue in the first place. We still can’t even replicate it…

    What is your theme and what other plugins are you running?

    Thread Starter Michael

    (@nikonratm)

    Thanks for looking into it. It’s a custom theme (I’m the developer) and lots of plugins active (but worth noting these are also active on the working site and none of them should be messing the the core admin role).full plugin list:

    Advanced Custom Fields Pro: by elliot condon – 5.3.5
    Ninja Forms: by The WP Ninjas – 2.9.33
    WooCommerce Availability Notifications: by ThemePlugger – 1.1.4
    WooCommerce Paymill Gateway: by Lee Willis – 2.6.1
    WooCommerce: by WooThemes – 2.5.3
    WordPress Post Type Archive Links: by Stephen Harris – 1.3.1
    Advanced Custom Fields: Ninja Forms Field: by bostondv – 1.0.2
    Advanced Custom Fields Pro: by elliot condon – 5.3.5
    User Role Editor: by Vladimir Garagulya – 4.23.2
    Ninja Forms – File Uploads: by The WP Ninjas – 1.4.6
    WooCommerce Table Rate Shipping: by Mike Jolley – 2.9.2
    WooThemes Helper: by WooThemes – 1.5.9
    Google Analytics Dashboard for WP: by Alin Marcu – 4.9.2
    BackWPup: by Inpsyde GmbH – 3.2.5
    ThreeWP Broadcast: by edward_plainview – 28
    WP-Mail-SMTP: by Callum Macdonald – 0.9.5
    WooCommerce Shipment Tracking: by WooThemes – 1.4.3
    iThemes Security: by iThemes – 5.3.2
    Redirection: by John Godley – 2.4.3
    User Switching: by John Blackbourn – 1.0.9
    ThreeWP Broadcast Premium Pack: by edward_plainview – 27.2
    WooCommerce – All in One SEO Pack: by Visser Labs – 1.3.4
    Jetpack by WordPress.com: by Automattic – 3.9.2
    W3 Total Cache: by Frederick Townes – 0.9.4.1
    All In One SEO Pack: by Michael Torbert – 2.3.1

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    If you remove the is_object check, does the error come back?

    Thread Starter Michael

    (@nikonratm)

    Just checked again, yep =/
    http://imgur.com/EPwK0gt

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    Which AIOSEOP version are you on?

    Thread Starter Michael

    (@nikonratm)

    2.3.1

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    2.3.2.x should fix it.

    Thread Starter Michael

    (@nikonratm)

    Awesome, thanks!

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Fatal Error add_cap() on a non-object in v 2.3.1’ is closed to new replies.