If you suspect content-specific issue, I’d first try to start with clean site and set of test content instead ( official Theme Unit Test data for example). If processing content is indeed at fault this is quite unusual issue. If you can narrow it down to specific function it might be possible to build some … Read more
404 is failure to communicate with the server. So either your configuration is not complete for the new server (for ex: permalinks), or your server needs optimization. You could try checking the server error log or php error log first.
(1) edit wp-settings.php [32M to 64M] (2) Try adding this line to your wp-config.php file: define(‘WP_MEMORY_LIMIT’, ’64M’); (you already have this, therefore ignore this step) (3) If you have access to your PHP.ini file, change the line in PHP.ini If your line shows 32M try 64M: memory_limit = 64M ; Maximum amount of memory a … Read more
Did some profiling, it was the 5k+ queries being stored in the $wpdb->queries array.
The short answer is no. The long answer is “it is complicated”. The memory limit is there to protect you from malfunctioning code eating all your available memory, something that will make your site less responsive for a while. (I tried to explain the issues around this setting here) This setting will not matter if … Read more
I’m wanted to comment rather than answer as I don’t have a solution for you, but I think this is too long 🙂 Hosts vary so widely on how and where they set memory allocation, and whether they allow hosted scripts to set it, that I don’t think there is a bullet-proof solution for you. … Read more
WordPress keeps crashing my server
WP_MAX_MEMORY_LIMIT in wp-config.php seems to be ignored
CPU Resource Management For Bulk Attachment Insert Share Host
Fatal error: Allowed memory size of bytes exhausted (tried to allocate 36 bytes)