[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.

[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]

This reply is private.

[Hill]

Had the same issue with recently that came along with “out of memory errors” and the extremely annoying “reoccurring events bug”. Might have been related, maybe not, but in the process i changed my .htaccess file to a default one and that fixed the problem for me, YMMV. Still working on the other fixes and removing 12,000 reoccurring events. Good luck.

[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…

[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]

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]

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]

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]

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]

Hi Cliff,

Great ideas…unfortunately neither worked for me.

So here is my setup. This is in my functions.php file.

// Show Featured Events before the Tribe Bar
function lrta_add_featured_events() {
	get_template_part( 'tribe-events/featured', 'events' );
	wp_reset_postdata();
}
add_action( 'tribe_events_before_template', 'lrta_add_featured_events' );

This calls the file my-theme/tribe-events/featured-events.php. The code is found in my previous post.

Thanks again for helping to track this down.

[Hill]

This page is stored in my child theme in the tribe-events folder.

[Hill]

Cliff,

I do have an Event Category called ‘Featured’, id=112. Here’s the custom code that I’m using to query the events and display them in divs.
https://gist.github.com/dheckel77/4affcc9548afa7796e32
It appears that the variable tribe_eventcategory on line 10 is getting over ridden by the page url. How do I make that static?

[Hill]

Sorry for the confusion on the “10,2” as I was trying different things at the time I grabbed that file. I don’t have any parameters in there now.

I did install the plugin that you sent earlier which works great but my challenge is that my client wants to have the Featured Image displayed and that is not an option using the Events List widget item.

Here is a screencast of what I’m seeing on my side. http://www.screencast.com/t/5byO5drex Hopefully this, along with the files I sent earlier will help pinpoint what’s going on.

Thanks again for all you help with this and I’m really diggin this plugin.

• This reply was modified 10 years, 3 months ago by Hill.

[Hill]

Thanks Cliff for the reply and the plugin. I’m able to hook into the tribe_events_before_template as can be seen at http://ltdstaging.com/events/ but my problem is that my query is somehow hooked to the filter bar query. The Event Category from the filter bar is overriding my query. Here’s my code that I’m using and my function that I call it with.

// Show Featured Events before the Tribe Bar
function lrta_add_featured_events() {
	get_template_part( 'tribe-events/featured', 'events' );
	wp_reset_postdata();
}
add_action( 'tribe_events_before_template', 'lrta_add_featured_events', 10, 2 );

How do I seperate the 2 queries? Also, am I using the right variable name for the event category in my args?

Thanks

• This reply was modified 10 years, 3 months ago by Hill.
• This reply was modified 10 years, 3 months ago by Hill.

[Author]

Posts