WordPress.org

Ready to get started?Download WordPress

Forums

The Events Calendar
[resolved] Notice: Undefined property: WP_Query::$tribe_is_event_query (6 posts)

  1. box
    Member
    Posted 12 months ago #

    wp-config.php

    define('WP_DEBUG', true);

    Notice: Undefined property: WP_Query::$tribe_is_event_query in .../wp-content/plugins/the-events-calendar/lib/the-events-calendar.class.php on line 2118

    Please change
    if ($query->tribe_is_event_query)
    to
    if ( ! empty( $query->tribe_is_event_query ) )

    http://wordpress.org/extend/plugins/the-events-calendar/

  2. jonahcoyote
    Member
    Posted 11 months ago #

    Hi box,

    Is this still an issue in 3.0.1? We're also releasing a new version today that may fix this. Keep an eye out for it and let me know if it fixes things.

    Thanks,
    Jonah

  3. Austin Passy
    Member
    Posted 11 months ago #

    I just posted a new thread before I saw this one. Oops.

    I can confirm the issue is still there in 3.0.2.

    http://wordpress.org/support/topic/php-notice-undefined-property-wp_querytribe_is_event_query?replies=1

  4. box
    Member
    Posted 11 months ago #

    I just updated the plugin and noticed that the bug is still there.

  5. roblagatta
    Modern Tribe Support
    Plugin Author

    Posted 11 months ago #

    Hey guys. Thanks for the follow-ups here. Jonah (who was previously handling this thread) has since left the team, but I want to follow-up and drive it to completion for you. I've got a note in with the devs and should have an update in some capacity for you by this time tomorrow. Appreciate your patience on this end so far.

  6. Barry Hughes
    Member
    Plugin Author

    Posted 11 months ago #

    Hi everyone,

    Notices like this one help developers to identify potential problems but don't necessarily indicate that there is any actual problem. So, ordinarily, the plugin will be operationally unaffected by this (there are some exceptions such as prematurely causing headers to be dispatched or "fouling" ajax responses, though).

    Best advice in the context of a production (or live) site is to turn off the display of errors. If you require WP_DEBUG to be on within a development environment - and don't want strict or notice level error reporting - you would have to either use a PHP directive to set the error reporting level appropriately such that it cannot be overriden during execution, or else set it with ini_set() after WordPress carries out its error-level setting magic, from either an early-running action or even within a mu-plugin.

    As Rob noted we have talked to the dev team about this and they will indeed be driving forward a cleanup to help ensure compliance with strict coding standards - so although you may not see a change in the very next release this sort of thing will definitely be addressed in the not too distant future.

    Thanks!

Reply

You must log in to post.

About this Plugin

About this Topic