This time it got stuck very long time on 39% when processing wp_post. It was not stuck completely, but every line took very long time compared to when I created the staging site a couple of weeks ago.
Hi @joelmellin ,
You have many WP Rocket-related errors, and memory consumption is high due to these errors. The memory consumption leads to this issue.
Increasing the memory limit from 128 to a higher value may help. Please follow the tutorial to resolve the memory exhaust error.
We have also received your free support ticket and will assist you further from there.
Cheers
Fayyaz
We already have 512 MB memory limit for PHP and for WordPress backend.
Where do I see the WP-rocket related errors?
You replied to us over email:
“I have gone through the debug logs and found the followings errors and warnings.
Allowed memory size of 536870912 bytes exhausted (tried to allocate 245760 bytes) - File: /home/mellins/public_html/wp-includes/class-wpdb.php Line: 2320
Class __PHP_Incomplete_Class has no unserializer - File: /home/mellins/public_html/wp-content/plugins/wp-staging/Framework/Database/SearchReplace.php Line: 203
It happened due to the Elementor fatal error, query limit or low server resources. Can you please share the temporary WordPress login details.
I can quickly look into that further and help you resolve.”
Have you been able to log in and do more investigation? Are you sure about it is because of WProcket, since you also for example mentioned Elementor? I just want to know if I am going to write the WProcket support and also what to write to them so that they understand the problem.
Hello @joelmellin
we’ve replied to you via email. So I am closing it here.
All the best
René
