|
October 26, 2021 at 3:52 am
Hi there,
The first thing to do before moving forward is to back up at least the database, I’d likely do a full site backup just to be safe, but the database is a minimum.
Site is as upto date as it can be with sll the issues whicj are failing to load.
My apologies but I don’t understand this, can you add some more details?
I can probably answer my own issue by decalring hosting is not good enough as always hitting the 100% CPU limit, but what is causing this is another matter.
There are many possible causes for hitting 100% CPU but the number of registrations in your database should not be one of them, 3800 isn’t all that many in terms of what the database should be able to handle.
I’m not sure what type of hosting you are using but have you contacted your host to see which processes are sitting using the CPU?
Because of the site instability, this is going to take forever. I understand that it was the case that there was no global deletion process. Has this changed?
I’d recommend putting the site into maintenance mode whilst working on it.
For example, use a plugin like this:
https://wordpress.org/plugins/wp-maintenance-mode/
Set the site into maintenance mode with your own custom messages showing that you are currently working on the site and will be back soon. If the site is throwing various errors whilst visitors are viewing pages the above is no worse than them viewing half a page or no page at all with an error.
If the CPU issue is from visitors, that should also help manage the load a little better whilst you work on it.
Because of the site instability, this is going to take forever. I understand that it was the case that there was no global deletion process. Has this changed?
We don’t have a global option, but in version 4.10.13.p and above you can permanently delete an event which will then also delete the data related to it (registrations, datetimes, payments etc) but not the EE_Contacts related to that data.
So for example if you go to Event Espresso -> Events.
Hover over an event and click trash.
It moves the event to be ‘soft deleted’ (meaning its marked as deleted and sits in the trash).
If you then click the Trash filter at the top of the event table you can perm delete the event there: https://monosnap.com/file/1jirv7TqYMiqwTN1W62fnLbfj2xsgz
When you click that EE should evaluate what needs to be removed and give you a breakdown, like this: https://monosnap.com/file/EamapS7X9wJeaGHYX2z6jgueiIAJ6r
Note the checkboxes, we recommend creating a database backup before using this feature, you should have one from above in this case but even if you are only deleting a single event, it is still recommended to backup first. The commands are removing a lot of data from the database, we can’t bring that back so if needed the only way to get that data is from a backup.
Click to delete and the match system will process everything that needs to be deleted.
That needs to be done individually per event but is quicker than removing individual registrations etc.
Is it likely the number of registations and events would slow the site down?
No, at least not in my opinion.
|
