Hi, I recently had to add the line:
define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
to all my live sites because MainWP plugin requires at least 64MB. I’m not sure why this line doesn’t appear by default in the wp-config.php but I’d like to add it to the one used for my blueprints so that I don’t have to add it manually to each site I’ll be creating. Before doing so, I just wanted to check and see if there are any known issues related to doing so and using Flywheel?
You shouldn’t run into any issues with this. The worse thing I can think of is that it simply doesn’t take effect.
For posterity, sites in Local by Flywheel default to
They default to 256MB? Ohhh… then how come this doesn’t show in the wp-config and I have to add that DEFINE line manually? I figured if I had developed in the default environment of 256, that it would carry over with my deployed website?
(newbie here so a little explanation would help!)
The memory limits are different on Flywheel since there are different plans and site sizes.
The override in
wp-config.php should work fine (up to a certain point). You can always contact Flywheel support regarding the memory limit on the live Flywheel and they should be able to help out.
when you say “should work fine (up to a certain point)”, what does that mean? can anything negative come from having the 256MB defined explicitly in the wp-config?
Sorry for the ambiguity!
On Flywheel, you should be totally fine with
256MB. With “up to a certain point”, I mean adjusting that to a much higher number like
1024MB will be ignored if it’s above the server max.
Browser to php.ini file in your sites files
SITENAME/conf/php/7.0.3/php.ini open the php.ini file and change
post_max_size and then restart you sites again