HELP _ Events Calendar Plug-in permanently disabled by our hosting company!

[Brook]

This reply is private.

[Kelly]

I still have one question in regards to this particular question as copied below:
“Recurring event data is still being generated for this event. Don’t worry, you can safely navigate away – the process will resume in a bit in the background.” – after which the whole system locks up for about 6 minutes. Even ith the setting set to only one month in advance, this process doesn’t remove the 2year-out repeated events. This may have been there before but I never noticed it.
This was especially helpful to note. It was a great idea to change that setting. It has been part of our plugin for ages, but if you don’t need events 2 years out then modifying it down to a few months is clever. Setting it to 1 month for now does not hurt at all, and will cut down a little on the amount of time your calendar needs to correct things. Once it finishes correcting things those events 2 years out should disappear, but correcting stuff will take a while.

This seems to indicate to me that the fix should clean-up all of those recurring events that are beyond 1 month in advance? Is this correct?

[Brook]

Good question. I have to guess a little bit because I do not have a corrupted database on hand to test with. But I believe it will delete all recurrences that are greater than 2 months out when set to 1 month.

Ordinarily decreasing this setting would not delete recurrences, it would simply prevent further ones from being created until you are ~1 month out. However, the cleanup plugin is triggering a rebuild, and in theory that would cause the extra recurrences to disappear. If it does not, then editing an event series and hitting update definitely will cause that series to delete future instances.

Depending on your needs this might be a moot question. If your calendar was running fast enough before the update, and it’s only since the update that things slowed to a crawl, then deleting those extra 23 months is not necessary to get things back to speedy.

Please let me know if you have any more questions before proceeding. Cheers!

– Brook

[Kelly]

Actually, it has been dragging down, slowly over the past few months. I noticed yesterday, when I created a new event, it was so fast, I couldn’t even believe it!
But yet, events that were created previously, are still scheduled out until April 2018. Which, of course, is not necessary. So, I am currently following your direction and updating one of the “offending” events (edit all), hoping that will clear things up.
Otherwise, my only option that I could see available was to sort by date, “select all” on one page and delete all. Then repeat for each page of the extra events. Then do that for each community which we have classes in. This could literally take me DAYS of doing just that. We have 100’s of communities with classes running 3 days per week. If you can imagine the size that this database has grown to because of this issue. I literally have 9-15 PAGES of 20 classes events for each community. And I just checked, we have 199 communities with classes running. I’m no math major, but 12 pages for each of 199 communities gets to be ALOT OF DATA. IF you can imagine why this bug stopped our website dead in its tracks…

[Kelly]

If I load any event, it gives me the “updating” message (Recurring event data is still being generated for this event. Don’t worry, you can safely navigate away – the process will resume in a bit in the background.). If I leave the window open, and check back periodically, the timer indicator does move. Often, it will give me a “connection lost because the process is taking too long”.
On the other hand, if I create a new event, it goes faster than it has ever gone before.
It has been approximately 72 hours that all the programs have been updated, and this process still appears to be going on in the background. Is there any way of telling if it is actually doing anything? 72+ hours seems like a LONG time, but not sure what would be expected?

[Brook]

I noticed yesterday, when I created a new event, it was so fast, I couldn’t even believe it!

This is really good news! Your site has been repairing itself as intended.

On the other hand, if I create a new event, it goes faster than it has ever gone before.
It has been approximately 72 hours that all the programs have been updated, and this process still appears to be going on in the background. Is there any way of telling if it is actually doing anything? 72+ hours seems like a LONG time, but not sure what would be expected?

That is a long time. It creates and cleans up recurrences in short few second bursts every so often. It is not constantly running in the background, rather it is running for brief moments periodically. But even still 72 hours seems longer than it should. I am wondering a few things that could shed light on this issue.

1) I wonder if you repeatedly refresh that page does it seem to be happening faster?

2) If it’s no trouble, could you ask your developer to run these queries again?

SELECT count(*) FROM wp_2_posts WHERE post_type = 'tribe_events'
SELECT count(*) FROM wp_2_postmeta WHERE post_id IN (SELECT ID FROM wp_2_posts WHERE post_type = 'tribe_events')

Could the dev also run this and let me know if the response is “complete” ?

SELECT option_value FROM wp_options WHERE option_name LIKE '_transient_tribe_63556_status'

Thanks again for working with us on this and your patience while we get everything sorted.

– Brook

[Kelly]

Nothing changes if I refresh the page.
The only time it appears to be doing anything is if I go into one of the classes and update. Otherwise, nothing seems to be going on.
I will ask the developer to run the query you requested.

[Brook]

Good to know. Thanks for getting back. Yeah if your developer can run those that would be awesome, it will shed a little more light into what’s going on.

• Brook

[Kelly]

Here’s the results of the query:

SELECT count(*) FROM wp_2_posts WHERE post_type = ‘tribe_events’
24,984 (was ~49,000 five days ago)

SELECT count(*) FROM wp_2_postmeta WHERE post_id IN (SELECT ID FROM wp_2_posts WHERE post_type = ‘tribe_events’)
434,231 (was ~914,000 five days ago)

SELECT option_value FROM wp_options WHERE option_name LIKE ‘_transient_tribe_63556_status’
returns “complete”

These notes from my developer:

So maybe it is still running? I’m not sure what the “complete” status means, but the data set is about halved so maybe in a few more days it’ll be finished running?

[Brook]

Ahh very good to know, thank you.

So maybe it is still running? I’m not sure what the “complete” status means, but the data set is about halved so maybe in a few more days it’ll be finished running?

The “Events Calendar PRO: Recurrence Events Rebuild” plugin would have finished it’s course if the status is complete. But it is probably in no small part responsible for the # of posts being cut in half.

I did some tests yesterday on the fastest way to rebuild those recurring events, so you’re not waiting 72 hours for each one and you don’t have to do it for multiple pages. What I found was that that this plugin will indeed eliminate all those events that are 2 years out if you have already changed the setting from 1 month to 2 years. If I were you I would make sure you have that setting where you want, if you only want events 1 month out then great! Now I would tell the plugin, which has currently stopped running, to start again. You can do this by running this query:

DELETE FROM wp_options WHERE option_name LIKE '%_tribe_63556%'

A note for your developer: Please make sure you are comfortable with your database backups before running a delete query. The above should have no ill side effects, but it is very common for website to backup before running queries like the above just in case the unexpected happens.

Once that query has been run your website will start gradually deleting all of those event recurrences from 2017 and 18. You will not have to do so manually. Best of all it should be doing it much faster than 72 hours per event. And finally when it is done running, your site will be faster than ever. It might take it a few days to finish, but of course your developers can rerun the above queries at any point to get a status update. If the status is not “complete” it will be empty, and if it’s empty it is still running.

Does that sound like a plan?

Cheers!

– Brook

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Author]

Posts