EC Pro 4.4.9 & Divi Theme 3.0.50 Issue

[Michael]

After upgrading EC Pro to v4.4.9 and the Divi WP Theme to 3.0.50, am getting an HTTP 500 error when accessing any page on the site, whether it has an Events Calendar component or not.

I have determined that the issue is the EC Pro plugin by inactivating all the plugins and activating them one by one.

This does not occur if I restore the Divi theme to the previous version. It also does not occur if I upgrade EC Pro but not the Divi theme.

I realize that this may be an issue with the Divi theme, but since all of my other plugins work with this upgrade, I thought I should start here.

[Michael]

Can I have this reviewed by EC Pro support, please? I am unable to use new features in my theme.

[Cliff]

Hi, Michael. Sorry for the delayed reply here. And sorry you’re experiencing this.

This isn’t currently a known issue so I’d suggest following these recommended troubleshooting steps for your own site:

There might be some new updates available. Could you please make sure all your Modern Tribe plugins (and WordPress core) are at their latest versions?

• Downloads / Version Numbers
• License Keys
• TEC Automatic Updates
• or TEC Manual Updates
• WordPress core updates

Once you verify you’re on the latest versions, please test to see if the issue is still happening for you.

If it is, please follow our Testing for Conflicts Guide (basically switch to Twenty Seventeen theme and deactivate all plugins and custom code other than Modern Tribe plugins) and see if that helps narrow down the cause of this.

Of course, we always recommend restorable database and file backups before modifying anything on your site.

If it doesn’t, please enable WP_DEBUG and WP_DEBUG_LOG (which will create a file on your server at /wp-content/debug.log if there are any WP_DEBUG messages) and share any debug messages you see while trying to replicate this issue and doing other things on your site relevant to this ticket (such as visiting your site’s home page, events page, single-event pages, and anything else you can think to do).

Then, please share your System Information (while in Testing for Conflicts Mode) in a Private Reply. That will give me a lot of extra information to help troubleshoot this.

You might also see if you can spot any console errors at your site. (If needed, you may reference our KB article Using Google Chrome Developer Tools.)

Let us know what you find out.

Thanks.

[Michael]

Hi Cliff,

Sorry for the delayed response to your posting. I’ve been working on some
other items on my test site and wasn’t able to conduct any testing.

I had conducted a number of tests to determine which plug-ins and in what
combination were causing the HTTP 500 crashes. It was quite confusing,
because various combinations were causing a crash. For example, just the
new Divi theme with TEC and TEC Pro would crash. Restoring to a previous
Divi theme or previous versions of TEC all worked. I was unable to test
with the TwentySeventeen theme because TEC widgets were placed in custom
widget areas in Divi. I didn’t want to recreate everything in that theme.

Finally I decided to install a 3rd environment on a locally hosted
environment and, voilà, everything worked as it should, no crashes. That
led me to look at the hosting versus local environment. What I realized was
that the hosted environment was running PHP 7.0 and the local environment
was running PHP 5.5. Switching my hosted environment to PHP 5.5 solved the
issue.

Clearly, something in PHP 7.0, with newest Divi and TEC (and possibly some
other plugins) was creating a conflict. Just as an aside, when the HTTP 500
errors were thrown, I also received messages from my uptime monitor that
the site was not responding. Therefore, something was definitely causing
the site to come full stop.

The bottom line is that all is well. I will keep my PHP version at 5.5.

I hope this long explanation helps if others are having similar issues.

[Cliff]

Kudos on your good sleuthing. Thanks!

We don’t have any reported bugs like this, even on PHP 7.x

Of course PHP 7+ is recommended, but we usually test with it too and don’t have any bug like this currently logged. Maybe it’s Divi that has a PHP 7 shortcoming?

Do you still get errors with PHP 7 even when our plugins are deactivated?

[Support Droid]

Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

Thanks so much!
The Events Calendar Support Team

[Author]

Posts