Please fix warning: ‘Undefined property: WP_Query::$tribe_is_event_query’

[Steven Kaufman]

I note that you advise people to deal with this by turning off WP_DEBUG. However leaving this warning to be ignored caused an unexpected outcome, and I lost the ability to edit images in the media library until I changed your code (following the fix from this post: http://wordpress.org/support/topic/notice-undefined-property-wp_querytribe_is_event_query).

Does this “cure” cause any other problem, aside from the inherently undesirable fact of hacking your plugin?

[Kelly]

Hi, Nabha. Thanks for getting in touch.

First, let me assure you that we are currently working on revising our code to make TEC/ECP strict-standards compliant. We aren’t there yet, but expect to be in the near future.

In the interim, we currently advise users that turning off error display is a better solution than hacking the code yourself. Note that this is different from disabling WP_DEBUG.

The behavior you’re seeing after defining WP_DEBUG as false has this effect in some environments but not all. So, if you are finding that measure doesn’t solve this, you would probably do better to seek advice from your host on turning off the display of errors.

Hope that helps!

[Steven Kaufman]

Thanks for your reply, Kelly. I want to clarify that on the live site WP_DEBUG is defined as false, but the image editing does not work. After this change to the plugin it does work. It was on the dev site that I was able to identify the warning.

I appreciate knowing that the team is working on it, and I just wanted to add the info that the implications go beyond error display.

[Kelly]

Thanks, Nabha. We appreciate the clarification!

[simpleconnections]

With 3.8 released just last week, I’m surprised this wasn’t addressed, requiring me to update your code to handle this error cleanly. Any idea when this will be updated?

[Brian]

simpleconnections,

I am not sure if it was addressed or not. I did a test on a development site and it did not return any notices related to this.

SInce, this is an old ticket so I am going to close it. I am also closing it because if you reply here our system may not pick it up, but if you could create a new ticket with the line you modified and under what conditions you site has we will take a look to fix this.

Thanks

[Author]

Posts