Upgrade to 3.1 Fatal Error

I had the same thing happen to me.

Does anyone have a fix, I want to continue using this plugin

I’ve downgraded for the time being.

I’ve confirmed the fixed posted on tribe’s website doesn’t fix the fatal error issue.

https://tri.be/fix-for-static-front-page-being-overridden-when-including-events-in-main-blog-loop/

Hi Jordan: I don’t believe that fix relates to a fatal error and so what you are experiencing is probably quite separate.

Can you try deactivating all other plugins and switching to a default, unmodified theme (such as Twenty Twelve) then see if you can activate The Events Calendar 3.1 at that point?

Sure, I will let you know how it turns out.

Great!

I am having the same issue as well. Only on my blog page (index only, single blog posts work fine as well). I deactivated all plugins and it still occurs. I switched to the default theme and the error went away.

Any thoughts? Must be something in my “tribe-events” folder. Has there been any functions or calls that have been removed that may be causing this error?

Also if I downgrade to 3.0.3 there is no issues.

Hi Mark__G – I’d recommend following the same troubleshooting steps as outlined for Jordan. You’re more than welcome to monitor this thread of course but, to avoid confusion, if you need further assistance it would be appreciated if you could post a new thread of your own.

Thanks!

Disabling all of the plugins doesn’t fix the issue. Changing the theme does, and my theme does modify the $wp_query which I assume is causing the error message. What modifications do I need to make to ensure that the plugin works correctly?

What modifications do I need to make to ensure that the plugin works correctly?

Well, unfortunately we can’t really guide you through that – because it would require a review of the theme’s code and we’d need to figure out why they are doing this and what the ramifications of stopping it are.

Generally speaking and going off past experience, though, removing this behaviour from the theme and changing it so it operates only on a custom query object of its own has resolved things – however this may not hold true in every single case.

Can the theme author shed some light on why they need to do things this way?

The theme was custom built off of the TwentyTwelve theme.

They were messing around with wp_query and this was causing the problem, once this was cleaned up and not touched, things started working correctly again.

Great – and thank you for reporting back.

So is Twenty Twelve itself a problem? or other wp_query shenanigans on top of that? My Twenty Twelve child theme is doing the same thing.

It’s most likely your child theme, not the Twenty Twelve theme. Look for any wp_query bits and make sure that you’re not modifying the $wp_query variable.

Great advice!

Please also remember that it’s generally best, per www.remarpro.com forum rules, to create a new thread of your own – even if on the surface it looks similar to an existing report.

Thanks!