500 server errors when updating more than 50 products with variations

Site seems to work OK, with two processors and 4 GB Ram. MySQl on same server at the moment but if I use the standard woo-commerce bulk edit on more than 50 t-shirts each with 65 variations, it runs for ages and eventually fails with simple “this website is not responding” error 500

If I Htop my server, the processors are maxed at 100% and memory around 50%

In my wp-config file at the top I have:

define(‘WP_MEMORY_LIMIT’, “2048M”); ini_set(‘memory_limit’, “2048M”);

Yes thats 2GB to Word-press?? Is that too much and stealing from MySQL?

Its a multi-site install that I haven’t finished the other installs so they are not being hit at all. I have this in my wp-config file: define( ‘WP_ALLOW_MULTISITE’, true ); define(‘MULTISITE’, true); define(‘SUBDOMAIN_INSTALL’, false); define(‘DOMAIN_CURRENT_SITE’, ‘’); define(‘PATH_CURRENT_SITE’, ‘/’); define(‘SITE_ID_CURRENT_SITE’, 1); define(‘BLOG_ID_CURRENT_SITE’, 1);

Also have this

/** Sets up WordPress vars and included files. */ require_once(ABSPATH . ‘wp-settings.php’); define(‘CONCATENATE_SCRIPTS’, false);

My PHP.ini has silly settings such as

max_execution_time = 30000 max_input_time = 60000 memory_limit = 512MB

I really get the feeling this is MySQL related but by php.ini settings and word-press memory limits might be creating this issues


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Accepted Answer

You will find that the iniset is most likely a WordPress wrapper for the php ini_set function (so it is trying to increase the memory limit to 2GB for PHP at execution time (although most php configurations running in safe mode would block this). As I understand it, WooCommerce and its bulk operations are fairly resource intensive.

It might be opportune to try adjusting the settings in php.ini directly:

  • Increase Memory Limits over server to 512M, 756M and switch them back after its deleted.
  • Increase Max execution time, this dimension of time is vital too in successfully executing a script over server. Increase this value to 60 (60000), 120 (120000) etc. And switch it back when you are done.

Here is a good guide on How To Change Your PHP Settings on Ubuntu 14.04, if you are unsure. Don’t forget to restart your web-server after making the change, so they can be applied.

I understand that are also plugins that help with these type of operations, as it is a common theme that they crash the php parser, you might want to check out Sheet Editor for WooCommerce. It seems to be written just for these types of problems.

If all this doesn’t work, just edit the products in smaller batches and see if that completes successfully.

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel