When dealing with any server configurations you want to setup some sort of safety to avoid this kind of processes running infinitely. PHP already provides you some tools to do it, and it’s pretty easy. – exit_on_timeout – max_execution_time You will need to find a safe spot for what you are running inside of your … Read more
Allowed memory exhausted is generally generated because the server can’t handle the memory usage of your site, and the actual memory issue can, as Pieter Goosen mentioned, really be anything on the site. Answers to your questions: It’s not too many plugins. WordPress can handle it 🙂 Probably not. If the storage of your website … Read more
You need to increase the php-memory-limit you can find out how much you have now with <?php phpinfo(); ?> Edit php.ini .Search “memory_limit” in your php.ini, and change the value of it. If no “memory_limit” found, add the following line at the end of php.ini memory_limit = 128M ; /* Change the 128M to your … Read more
Turns out this issue was caused by bad code (a missing assert) in my theme. More specifically the theme requires a custom navigation menu. As this menu hadn’t been created and assigned the site crashed. Why this caused an memory exhaustion error on my production server and not my development computer I unfortunately don’t know.
Try adding to wp-includes/default-constants.php You’ll probably see the default values of 40M starting around line #20, change these values. My setup is as follows: // set memory limits if ( !defined(‘WP_MEMORY_LIMIT’) ) { if ( is_multisite() ) { define(‘WP_MEMORY_LIMIT’, ‘256M’); } else { define(‘WP_MEMORY_LIMIT’, ‘256M’); } }
Try to create .user.ini file in root and put below code upload_max_filesize = 500M post_max_size = 256M memory_limit = 500M max_execution_time = 300 max_input_vars = 500M Try and let me know if any query. Hope it will help!
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.