- This topic has 3 replies, 2 voices, and was last updated 13 years ago by
.
-
Posts
-
I just purchased Events Calendar Pro a few days ago and just now upgraded to V3 + Pro and I am getting this string of messages, V2 worked great (I was/am still in setup mode) – Any suggestions/ideas? Thank you.
Notice: Undefined property: WP_Query::$tribe_is_event_query in /home7/webmasw4/public_html/reddingweekly/wp-content/plugins/the-events-calendar/lib/the-events-calendar.class.php on line 2117
Notice: Undefined property: WP_Query::$tribe_is_event_query in /home7/webmasw4/public_html/reddingweekly/wp-content/plugins/the-events-calendar/lib/the-events-calendar.class.php on line 2117
Warning: Cannot modify header information – headers already sent by (output started at /home7/webmasw4/public_html/reddingweekly/wp-content/plugins/the-events-calendar/lib/the-events-calendar.class.php:2117) in /home7/webmasw4/public_html/reddingweekly/wp-includes/pluggable.php on line 876
Hi Nigel,
It’s great to have the display of errors turned on when in development (as of course you are) however notices like these – though ideally we wouldn’t be generating any – aren’t necessarily indicative of any deep problems as such.
In this particular case, because they are being displayed, they are stopping header information from being sent (as the notices are being printed before the code changing the headers is run) – but turning display_errors off would remedy this.
The process for this varies from host to host. Sometimes it can be done by simply changing wp-config.php so that the WP_DEBUG constant is set to false, or else you may need to do it from within your .htaccess or php.ini file – the best thing though is to get in touch with your host on this one.
I’ll definitely make a note for the dev team to investigate the generation of the notices here, however – thanks for reporting – and let me know if the above doesn’t help here.
- The topic ‘Upgrade to V3 – broke site’ is closed to new replies.