WordPress.org

Ready to get started?Download WordPress

Forums

Co-Authors Plus
v2.6.1 update breaking site with array error/plugin conflict (5 posts)

  1. mcstevem
    Member
    Posted 2 years ago #

    Updating Co-Authors Plus to v2.6.1 has triggered a conflict with the More Taxonomies v1.1 plugin, littering my site's pages with dozens of instances of this error message:

    Warning: call_user_func_array() expects parameter 1 to be a valid callback, first array member is not a valid class name or object in /home/ucbnews/sandbox/wp-includes/plugin.php on line 170

    I realize that More Taxonomies has not been updated in months, and that comments in their forum indicate it is not a cleanly coded plugin. Still, CAP and MT played nicely with each other on my site until the latest CAP update. And both of them provide important functionality to my site, so before I could remove one I'd have to find an alternative way to provide the same function. Any easy suggestions on how to restore harmony to the neighborhood?

    http://wordpress.org/extend/plugins/co-authors-plus/

  2. iamskwerl
    Member
    Posted 2 years ago #

    Just stumbled upon this same issue and found this post while looking for a solution. Subscribed, and I'll see if I can come up with a workaround.

  3. iamskwerl
    Member
    Posted 2 years ago #

    OK, I actually managed to find a fix already. More Taxonomies was easier to reverse engineer, and it appears to deserve more blame than Co-Authors Plus. It's running a function called set_default_data at a priority of 1, which seems to be collecting custom taxonomies, but somehow clobbering the co-author ones. If you set its run priority to run later, the issue goes away.

    So open up more-taxonomies-object.php in the More Taxonomies plugin folder, and edit line 10, from:

    add_action('init', array(&$this, 'set_default_data'), 1);

    To:

    add_action('init', array(&$this, 'set_default_data'), 100);

  4. Daniel Bachhuber
    Hand Built
    Plugin Author

    Posted 2 years ago #

    Hmm... I wonder what changed in v2.6 that caused issues. I don't remember changing around the custom taxonomy declaration at all; most of the work was just cosmetic features.

    Any ideas?

  5. mcstevem
    Member
    Posted 2 years ago #

    Thanks, iamskwerl, that priority change worked for me, too.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic