Hi Gitte, I saw that button and used it on Simple Image Sizes Plugin to re-generate thumbnails, but after it ran I checked via SFTP and all the old ones were still there. It was not until I used the “Regenerate Thumbnails” plugin that the old ones were deleted. Perhaps this is unique to my server environment on WP Engine but I’m just glad to have the disk space cleaned up.

Thanks for your help!

Thanks Gitte, and then to re-generate the older media files already uploaded, do you use regenerate thumbnails plugin?
I’m a bit concerned that the plugin you are recommending has not been updated in a long time and has not be certified to be compatible with WP 5.0…?

Ismael, thanks so much. However I want to keep some of Enfold’s sizes.
It sounds like this will eliminate all the theme’s sizes?

I would like keep all except:
– portfolio
– portfolio small
– gallery
– entry with sidebar
– entry without sidebar
-shop thumbnail
-shop catalog
– shop single

Do I need to customize the above code?

Thanks for continuing to work with me on this…. !

Cheers
Rob

OK I added the below code to functions.php on my child theme and nothing changed… I uploaded a photo and all the sizes were generated when I SFTP in and look at the directory:

function ava_image_sizes() {
remove_image_size(‘magazine’);
remove_image_size(‘widget’);
remove_image_size(‘portfolio_small’);
remove_image_size(‘gallery’);
remove_image_size(‘entry_with_sidebar’);
remove_image_size(‘entry_without_sidebar’);
remove_image_size(‘shop_thumbnail’);
remove_image_size(‘shop_catalog’);
remove_image_size(‘shop_single’);
}
add_action( ‘after_setup_theme’, ‘ava_image_sizes’, 11 );

What did I do wrong?

Thanks,
Rob

According to the Regenerate Thumbnails Plugin, here are the sizes currently configured in Enfold:

“Thumbnail Sizes
These are all of the thumbnail sizes that are currently registered:

thumbnail: 600×650 pixels (proportionally resized to fit inside dimensions)
medium: 300×300 pixels (proportionally resized to fit inside dimensions)
medium_large: 768×0 pixels (proportionally resized to fit inside dimensions)
large: 1030×1030 pixels (proportionally resized to fit inside dimensions)
widget: 36×36 pixels (cropped to fit)
square: 180×180 pixels (cropped to fit)
featured: 1500×430 pixels (cropped to fit)
featured_large: 1500×630 pixels (cropped to fit)
extra_large: 1500×1500 pixels (proportionally resized to fit inside dimensions)
portfolio: 495×400 pixels (cropped to fit)
portfolio_small: 260×185 pixels (cropped to fit)
gallery: 845×684 pixels (cropped to fit)
magazine: 710×375 pixels (cropped to fit)
masonry: 705×705 pixels (proportionally resized to fit inside dimensions)
entry_with_sidebar: 845×321 pixels (cropped to fit)
entry_without_sidebar: 1210×423 pixels (cropped to fit)
shop_thumbnail: 120×120 pixels (cropped to fit)
shop_catalog: 450×450 pixels (cropped to fit)
shop_single: 450×999 pixels (proportionally resized to fit inside dimensions)”

Hope that helps clarify.

Hi Ismael,
Thank you for the response!

Is there a way to do this without a plugin? Modify functions.php in my child theme? And are there additional sizes generated by Enfold for Woo Commerce?

Thanks!!
Rob

Sounds like WP Engine will upgrade us to 4.9.9 instead of 5.0.1 to address the security issues.

“WordPress Security Upgrade 5.0.1
Posted December 13th, 2018 11:59am

Maintenance is active
WordPress today has issued a security release to WordPress core, which fixes a few bugs. You can read more about this in WordPress’ official release post. We will be updating all customers on the 5.0 through 3.7 branch to the latest version of their branch. Your installs will be updated to their latest secure version of their specific branch. 4.9.8 for instance, will be bumped to 4.9.9. Please take a look at our WordPress Upgrade article here for more information on our upgrade process.

Because you are a WP Engine customer, you do not have to take action at this time. Our team is working to issue patches across the WP Engine platform to upgrade affected installs to their next stable version. We’ve got your back. As always, thank you for trusting WP Engine to host your WordPress sites. Automated maintenance updates like these are part of our promise to deliver a secure WordPress experience while ensuring the security of our customers.”

• This reply was modified 6 years ago by goldengate415.

According to their page, they handle security updates differently. I had selected the “defer updates” button when WP 5 came out and we saw the issues.

“SECURITY/MAINTENANCE UPDATES
This type of update contains security or minor fixes that are pushed out to repair a vulnerability or bug in the WordPress core. We immediately investigate that the change doesn’t adversely affect our platform then push it out to our customer’s installs. We have found that the vast majority of installs that are adversely affected by security updates are ones that are using the vulnerability that is being closed. Because of this, we cannot defer security updates as this would keep your site and our platform vulnerable. Given the timeframe, site administrators will only be emailed on the same day as the upgrade occurs.”

Full page here:

Having said this, the classic editor plugin seems to solve the issues I was having on ALB pages not loading, but the fact that there is an incompatibility makes me concerned to update to 5.0.1 until Enfold weighs in. I don’t think I will have a choice much longer according to WP Engine’s process.

Yes, that plugin fixes the problems! Mike, you might want to add that suggestion to the sticky. Much better than the “save and re-save” the page which didn’t work for me.

Cheers
Rob

Thanks Mike. The solution from 007 is not working for me on pages that I had already opened to test… perhaps it only works the first time a page is opened? In any event I will wait for 4.5.2 before installing WP 5.0 on my production site. :)

“Edit: if you first – when you open an existing Enfold ALB Page goto “Save” : “Update” Button on the right top side – then the page will be as it should be – and the image of text-block element would not be this way above:”