Viewing 7 replies - 1 through 7 (of 7 total)
  • This plugin seems to integrate with WP_Query, but relies on $wp_query being set in proxy to use of get_query_var().

    This plugin can either check if $wp_query is an object before calling get_query_var, or integrate with WP_Query further down the action pipeline.

    If this plugin runs it’s add_action for the WP_Query actions by adding the add_action for those actions during ‘init’, there should be no further conflict.

    Thread Starter lok1728

    (@lok1728)

    Thank you Scott for replying. I’m not sure where to change those items, but I’m hoping the developer can make the updates to resolve the conflicts. Thanks again!

    I double checked the code, at the bottom of the plugin’s main file this runs the init:

    $wpbdp = new WPBDP_Plugin();
    $wpbdp->init();

    One solution would be to place this line within the _plugin_initialization function instead:

    add_action('pre_get_posts', array($this, '_pre_get_posts'));

    Plugin Author Business Directory Plugin

    (@businessdirectoryplugin)

    Hi Scott,

    Thanks for the info, we’ll look to add it for a patch release. In the meantime, anyone can use the workaround outlined above.

    I’ve also made some tweaks to the next version of Pods which should hopefully resolve most of these issues as it runs further up the action chain itself too.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Conflict with PODS Plugin’ is closed to new replies.