WordPress.org

Support

Support » Plugins and Hacks » Yet Another Related Posts Plugin (YARPP) » [Resolved] Mistake after update

[Resolved] Mistake after update

Viewing 10 replies - 1 through 10 (of 10 total)
  • yup, I’m seeing the same error on my site

    same here

    same here

    Warning: in_array() expects parameter 2 to be array, null given in *****/plugins/yet-another-related-posts-plugin/classes/YARPP_Core.php on line 977

    Ditto here

    esmi

    @esmi

    Forum Moderator

    People!: If you require assistance then, as per the Forum Welcome, please post your own topic instead of tagging onto someone else’s topic. The more you post “Me too”, the less chance you have of anyone being answered.

    Since there have been over 2 million downloads for this plugin and it’s obviously incompatible with 3.9.1 that was just released today, does it really help the developer for every single user to open a new thread saying it doesn’t work with the new WP version? Understandable if it’s a configuration/compatibility error, but when something is giving everyone the same error after a WP update like this, it seemed more helpful to the developer to not blow up the forum topics with everyone posting the same thing. Was just trying to be considerate.

    esmi

    @esmi

    Forum Moderator

    does it really help the developer for every single user to open a new thread saying it doesn’t work with the new WP version?

    Yes – that’s how these forums work. As this topic now stands, it won’t attract a second glance., Too many people jumping in.

    Plugin Author jeffparker

    @jeffparker

    Thanks everyone for the feedback and the patience while we resolved. This was a bug pertaining to users updating from previous versions of YARPP. We have fixed the problem in version 4.2.1.

    Thanks, Jeff!

    Plugin Author jeffparker

    @jeffparker

    We just pushed out a stable 4.2.2 that takes care of the recent issues. Please upgrade and let us know what you think. Thanks!

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘[Resolved] Mistake after update’ is closed to new replies.
Skip to toolbar