Support » Plugin: Pods - Custom Content Types and Fields » [Plugin: Pods – Custom Content Types and Fields] Fatal Error get()

Viewing 15 replies - 1 through 15 (of 27 total)
  • Plugin Author pglewis

    (@pglewis)

    I’ve filed a GitHub issue: https://github.com/pods-framework/pods/issues/497

    We’ll get to the bottom of it.

    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    Hey there, looks like a very odd issue we haven’t yet seen on any sites before.

    Would you be open to letting me get in and fix it for you?

    https://podsframework.org/submit-site-credentials/

    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    I ended up patching with a fix which should resolve this. It’s in Pods 2.0.2, so please let us know if you have any further issues. Our top priority is ensuring no bugs like this occur for all of our awesome users 🙂

    Scott & pglewis, thanks for your help. The issue remains with Pods 2.0.2 I have submitted my info for you just now – Thanks!

    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    Didn’t get this notification e-mail yet so pglewis clued me in.

    Thanks for submitting your info, we’re very puzzled with the issue and want to get it resolved for you asap.

    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    It seems like an issue with another caching plugin, Quick Cache. Not sure what’s up there yet.

    stefwilliams

    (@stefwilliams)

    For the record, I get this issue as well, with Pods 2.0.4.1 on WP 3.4.2
    Am running Xampp lite and PHP 5.3.1.
    Will try installing on a full version of Xampp later and report back.
    I do not have Quick Cache installed, or any other caching plugin.
    Very few plugins installed in fact.

    stefwilliams

    (@stefwilliams)

    ok,
    tried it on my other install, and the same problem – Fatal error.
    The one thing I have in common with both installs is that I have Events Manager installed…
    Deactivate that and Pods seems to run with no problem. Activate one or the other and all is well…
    Activate both at the same time, and BOOM!
    Looks like they don’t get along…
    Any chance of fixing it? I have no clue what could be causing it myself.

    guix69

    (@guix69)

    same thing for me, events manager installed as well…

    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    Looking into this, we’ve done everything we can do to limit this kind of stuff from happening as all of our wp_cache calls have checks if the $wp_object_cache has been init yet. I’ll see if Events Manager isn’t doing that or something else is going on.

    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    This is the plugin you are all having compatibility issues with, right?

    http://wordpress.org/extend/plugins/events-manager/

    guix69

    (@guix69)

    exactly, thanks for looking into it.

    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    It looks like it’s the events-manager/em-ical.php file

    It’s doing something in parse_query that is getting messed up, but Pods doesn’t interact with parse_query or $wp_query. I’m still digging into it to see what’s going on.

    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    Pods makes a get_posts call before $wp_query is set, the Events Calendar plugin is hooking into parse_query but using a $wp_query variable check with get_query_var which fails, because $wp_query isn’t set yet. This seems like a bug with WordPress core itself really, but I’ll contact the Events Manager author with a workaround for him until then.

    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    I contacted the author, watch for an update soon from that plugin which should resolve this conflict.

    For now, just add this to a plugin, it disables the iCal from being available but both plugins will work until the update:

    function fix_em_ical () {
        remove_action ( 'parse_query', 'em_ical_event' );
    }
    add_action( 'plugins_loaded', 'fix_em_ical', 9 );
Viewing 15 replies - 1 through 15 (of 27 total)
  • The topic ‘[Plugin: Pods – Custom Content Types and Fields] Fatal Error get()’ is closed to new replies.