Skip to:
Content
Pages
Categories
Search
Top
Bottom

Conflict with All In One SEO?


  • cassel
    Participant

    @cassel

    Today, I noticed that when I click on the number indicating the notification on the WP bar on top, I get this error message:

    Warning: array_key_exists() expects parameter 2 to be array, boolean given in /home/creat419/public_html/scrapbookcampus.com/wp-content/plugins/all-in-one-seo-pack/aioseop_class.php on line 4735

    Warning: array_key_exists() expects parameter 2 to be array, boolean given in /home/creat419/public_html/scrapbookcampus.com/wp-content/plugins/all-in-one-seo-pack/aioseop_class.php on line 4735

    (yes, it shows doubled too, even if it is the exact same thing).
    I deactivated AIO SEO and the error is gone. So it is obviously a conflict with that plugin. When I installed BP a few weeks ago, that behavior was not happening so I can just assume it has to do with a recent update of one of the two.

    Is this just a bug?

    I cannot leave my SEO plugin deactivated as a solution (especially since it did work previously). Any suggestion?

Viewing 2 replies - 1 through 2 (of 2 total)

  • Boone Gorges
    Keymaster

    @boonebgorges

    Hi @cassel – Thanks for the post!

    I’ve just installed All In One SEO to try to reproduce. Looks like the line numbers have changed – I’m seeing 5711 now, instead of 4735! – but the error is still there.

    Looking into the all-in-one-seo-pack code, it appears that this error only occurs if you haven’t yet saved the options for this plugin. Once you’ve done so, the error ought to go away.

    For the record, I was able to trigger this notice even without BuddyPress.

    I’ve opened a ticket with the All In One folks to let them know about the bug on their end, so stay tuned at https://github.com/semperfiwebdesign/all-in-one-seo-pack/issues/2805 ! In the meantime, you might consider forcing errors not to be displayed on your production site – always a good idea. See https://www.wpbeginner.com/wp-tutorials/how-to-turn-off-php-errors-in-wordpress/


    cassel
    Participant

    @cassel

    I had also contacted the author for AIO plugin and they found it was actually a bug in their previous update (which was August 2nd). The issue was reported by several users and they were able to reproduce it. They have already fixed it with a newer update.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.
Skip to toolbar