mec_dates table in database

Hi @gdm57,

The only awkward thing is the number of records. Their number can vary according to the amount of information in events. Also, the type of repetition matters.

For example, if an event with all its content (date organizers, links, etc.) is due to repeat for two years every other day, this is a huge load of data. Multiply this to 303 and viola.

As WordPress can tolerate such a heavy load of information, it is neither an issue nor something awkward.

Best Regards

All of a sudden the calendar pages crawled to a stop. The mec_dates table had over 2.5 million rows!

Many of the end dates were in the year 2110. We cleaned out the table, deleting all the dates after 2025 and the records dropped to <10k and the site now loads reasonably well.

Turns out the weekly repeating events were created with the Never end date.

There must be some way to cap the end date for repeating event that doesn’t rely on the user to input a number or a date.

How about a code snippet to do that, or even better make it a settings option for admins?

We have a similar problem. The wp_mec_dates table grows very quickly, reaching 200 megabytes. The wp_mec_dates table grows very quickly, reaching 200 megabytes. Please, tell me how to solve the problem.

The increase in the size of the table mec_dates is due to many recurring events with the repetition term setting to “never”.
Just make them recurring for 4-5 years: otherwise they will be duplicated for more than 100 years from the date of the first event: none of us – and not even your sites – will still be active in more than 100 years.