Hello Mika.

Thank you for reaching out to us.

1. At the moment, there's no way to hide these events but our developers are working on redesigning the Events List form, so hopefully there will be more options in the near future.

2. This is most likely caused by another plugin, but either way, the solution here would be to increase the memory on your website. You currently have around 268MB of memory on your site, and Amelia tried to allocate 0.012288 MB but it failed. So, what Amelia tried to pull is not even 1/10 of a Megabyte, but it failed.

Please reach out to your hosting provider and ask them to increase the memory to at least 512MB.

Hi again.

In 90% of cases, the exhausted memory doesn't come from Amelia.

Can you please deactivate all other plugins except for our plugin, purge all cache, refresh the page, and see if it is resolved (it should be)? If it is, then start activating other plugins one by one, and after each activation refresh the page to see if the issue reoccurred. Once it does reoccur, you will have found the plugin causing the issue.

If you're still facing the issue even with other plugins disabled, that would mean that it's coming from Amelia, but I don't recall ever seeing that in the past.

There's no way to disable Amelia's functions in the back-end, but if you don't find a conflicting plugin, I'll reach out to our developers and see if there's anything we can do.

Hi again Mika.

I see. Once you're done testing the cloned website, could you send it to me so our developers can test it?

I just created a recurring event that repeats every day until December 31st, 2039 (6.126 events in total), and the back end still loads within 2 seconds.

That's why I have doubts this is coming from Amelia, but I can't be exclusive.

If you're sending us the login credentials for the staging site or the duplicator files, just make sure to enable the PRIVATE response, please.

Hello Justin.

Please open a private ticket about this (if you haven't already), and provide us with credentials for your site, and we'll gladly take a look.

Understood, Mika, thank you.

I forwarded this to our developers yesterday, and I'll get back to you as soon as I hear from them.

Hi, again Mika.

Our developers took a look and, as I suspected, it's the number of events returned.

They said there are approximately 4.000 events returned as the query retrieves all future events from *TODAY*.

This is called in the back end, so you can choose to preselect an event in the shortcode. We will look into optimizing this in a future update, to work with a large number of events, but I can't provide you with an ETA on that.

For now, you can access the file ../wp-content/plugins/ameliabooking/src/Infrastructure/WP/GutenbergBlock/GutenbergBlock.php and on line 223, you'll see this:

$events = $eventRepository->getFiltered(['dates' => [DateTimeService::getNowDateTime()]]);

Replace it with this:

$events = $eventRepository->getFiltered(['dates' => [DateTimeService::getNowDateTime(), DateTimeService::getNowDateTimeObject()->add(new \DateInterval("P1M"))->format('Y-m-d H:i:s')]]);

And it will pull only the events within the next month.

Please note that our developers already built the next update (6.2.2), so they won't be able to add this fix to it, but they will add it in 6.3. This means that, when you update Amelia to 6.2.2, you'll need to access the "GutenbergBlock.php" file and replace the line again.

I hope so too, Mika.

Please let me know if you face any other issues.