Newest version on events calendar AND calendar PRO (4.2.2) – memory errors

[Hill]

Hi,

Love your plug-ins, but the latest updated versions are causing memory errors (.php) completely disabling the calendar page on our site. All previous versions worked great. Is there an easy way to revert to a previous version fore the time being? Ive increased the memory limit on our server, but it still times out and all we see is a blank page or an error ( Fatal error: Maximum execution time of 30 seconds exceeded in /home/ltdstag2/public_html/lakesregion/wp-includes/functions.php on line 123 )

Please help. Thanks.

[Hill]

Additionally, in trying to install a previous version of the plug-in I am receiving this error message:

Request Entity Too Large
The requested resource
/wp-admin/update.php
does not allow request data with GET requests, or the amount of data provided in the request exceeds the capacity limit.

Additionally, a 413 Request Entity Too Large error was encountered while trying to use an ErrorDocument to handle the request.

[Hill]

OK, after some digging with my host, it seems as toough the error comes from the plug-in trying to retrieve a date stamp. Also, through my digging, i was able to make it display a “list view”. Anything with a visual calendar (month view, week view etc.) throws the error.

Also tried to downgrade the plugin to 4.2 and got the error below when trying to install from a file.

Request Entity Too Large
The requested resource
/wp-admin/update.php
does not allow request data with GET requests, or the amount of data provided in the request exceeds the capacity limit.
Additionally, a 413 Request Entity Too Large error was encountered while trying to use an ErrorDocument to handle the request.

[Hill]

Here’s an update: I’ve manually downgraded to version 4.2.1 by swapping out the folders in the wp-content>plugins>the-events-calendar and events-calendar-pro and the issue remains. Is there something i missed in the downgrade process? Like i said up thread, i cannot delete and reinstall the plugins via the wp backend as I get the “request entity too large” error.

I have upped the memory in the php.ini file as well as the execute time to 90 sec. I’ve also upped the memory in the wp-config file.

When looking at the error logs with my hosting provider (bluehost) it seems hard to track down the bug as it throws a different error every time it times out. The support tech seemed to think that the error had something to do with the events calendar plugin looking for a date stamp or timestamp and running itself out on that. If there is any more information you need, please let me know. My client’s site is updated regularly and i would hate to have to revert the site to a backup as we would lose a ton of information. Thanks in advance for your help.

[Hill]

If you go to this link: https://www.lakesregion.org/events/list/ and then use the view function to look at “month view” you will see what is happening. The top nav link (events) is a workaround so the viewer doesn’t see the error while we fix it. That link typically goes to the “events” (calendar-monthview) page.

[Hill]

And here is the error from our server log:

[Mon Jul 11 13:51:33 2016] [error] [client 2601:18d:8201:200:3c9f:849d:288b:d7a4] exec used but not allowed in /home/ltdstag2/public_html/lakesregion/500.shtml, referer: https://www.lakesregion.org/events/list/

[Hill]

also. I am getting the multiple event listings being created bug that everyone else on the forum is getting. Not sure if this is related or not…

[Hunter]

Hello and thank you for all the updates 🙂

For downgrading, we recommend doing so manually as instructed here.

Can you please confirm the issue occurs with only our plugins and the default WP theme active as outlined in our Testing for conflicts guide?

We just released a version that aims to address the recurring events issue, so please upgrade to version 4.2.2.1 and if you’re still having this specific issue, please create a separate thread and we’d be happy to investigate for you.

Lastly, send over your System Information as a private reply. Thank you again and have a good Monday.

[Hill]

This reply is private.

[Hill]

Yes, The error is still occurring with all plugins deactivated and the theme set to twentyfourteen. It seems as though, like all of the other posts with the “reoccurring events” bug, the bug is a total CPU sink and killing the processing power of the site. I’m hoping that after i go through and delete the 10,000 or so bogus events, the database will be freed up enough to run the plug-in.

If there is any more information you need, please let me know. I know you guys are having a rough day, but i really need to get this up and going ASAP. Anything i can do to move it along, I am more than willing to do. Thanks again.

[Hill]

OK. The ISSUE IS FIXED. Anyone who is having memory errors or timeout errors needs to look hard at the number of events that is in their calendar. The reoccurring events bug and subsequent version update will stop your plug-in from going rogue and filling your database with bogus events. BUT you will need to go in and manually delete (the batch delete and edit plug-ins referenced in a previous thread might work, might not – we had to do it the hard way) all of the bogus events (which is a horrowshow if you have a lot of legit events). Once you have deleted enough weight from the database, the plug-in will begin working again. We went from 12,000 events down to 3,500 before it started working again.

Unfortunately, I cannot get the two days of my life back that have been consumed by this issue. I would hope that the Tribe development team learn from this and thoroughly test their stuff before releasing. Sloppy work guys.

[Hunter]

Hey Hill,

We’re really sorry about the recurrence issue! We do our best to test for any issues before releasing, but they don’t call them bugs for nothin’ 🙂

Thank you for your patience and understanding on it though! We did put out a notice out on the 11th regarding the issue and it includes a way to automatically delete the events that were unnecessarily created. I understand for some users (such as yourself), it was a bit too late. So I must apologize again!

Thanks again for working with me on the issue and feel free to create a new thread if anything else pops up. Take care and have a good upcoming weekend!

[Author]

Posts