Tagged: Images
-
AuthorPosts
-
July 12, 2018 at 10:12 pm #984903
I have a publisher in the company that has put large images in the gallery (over 1Mb) Enfold then creates a number of image sizes from that. That makes for slower performance and bigger backups than the ISP is willing to support. My questions:
1. If I remove the originally uploaded image from the library, will the generated images and thumbnails also disappear?2. Then, if I reupload an edited image that is much more compact – yet looks good on the web, will Enfold regenerate those other images taking up correspondingly less storage?
3. Many site images are not going to be used for the big full page sliders – just for a 300×200 px blog entry (for example). Does Enfold need to generate all those other images, until the user has required a large image in the editor or in a slider?
Regards, Peter
July 13, 2018 at 7:31 am #984987I have this exact question – please let us know if there is a way to select or stop all the different image sizes being generated, as it is making the disk space for our websites max out!
July 15, 2018 at 2:34 am #985541Hi,
You can control which image sizes are created when you upload a image manually by commenting out the sizes you don’t want to use in /wp-content/themes/enfold/function.php$avia_config['imgSize']['widget'] = array('width'=>36, 'height'=>36); // small preview pics eg sidebar news $avia_config['imgSize']['square'] = array('width'=>180, 'height'=>180); // small image for blogs $avia_config['imgSize']['featured'] = array('width'=>1500, 'height'=>430 ); // images for fullsize pages and fullsize slider $avia_config['imgSize']['featured_large'] = array('width'=>1500, 'height'=>630 ); // images for fullsize pages and fullsize slider $avia_config['imgSize']['extra_large'] = array('width'=>1500, 'height'=>1500 , 'crop' => false); // images for fullscrren slider $avia_config['imgSize']['portfolio'] = array('width'=>495, 'height'=>400 ); // images for portfolio entries (2,3 column) $avia_config['imgSize']['portfolio_small'] = array('width'=>260, 'height'=>185 ); // images for portfolio 4 columns $avia_config['imgSize']['gallery'] = array('width'=>845, 'height'=>684 ); // images for portfolio entries (2,3 column) $avia_config['imgSize']['magazine'] = array('width'=>710, 'height'=>375 ); // images for magazines $avia_config['imgSize']['masonry'] = array('width'=>705, 'height'=>705 , 'crop' => false); // images for fullscreen masonry $avia_config['imgSize']['entry_with_sidebar'] = array('width'=>845, 'height'=>321); // big images for blog and page entries $avia_config['imgSize']['entry_without_sidebar']= array('width'=>1210, 'height'=>423 ); // images for fullsize pages and fullsize slider $avia_config['imgSize'] = apply_filters('avf_modify_thumb_size', $avia_config['imgSize']);
To comment out just place a // in front of each line.
But WordPress also creates some, so the best option to control both WordPress & Enfold is to use the plugin Simple Image SizesBest regards,
MikeJuly 16, 2018 at 2:55 am #985806Hi, this code worked perfectly for us to disable all Enfold-generated images sizes, add to functions.php.
//disables Enfold generating multiple image sizes
function avia_backend_add_thumbnail_size() {}July 16, 2018 at 12:31 pm #985908Hi,
Thanks for sharing your solution, unless there is anything else we can help with on this issue, shall we close this then?Best regards,
MikeJuly 16, 2018 at 5:47 pm #986013Thank you for the solution of modifying functions.php. Per my original question above, I’d like to know the purpose of all those images. Are they needed for making a responsive site for other devices, or are they just a convenience for faster loading? Or are they needed by the theme in some way that will later break the site? I’m trying to understand what I’m giving up by editing the functions.php
July 16, 2018 at 9:41 pm #986108Hi,
If I remove the uploaded image from the library (just like this: https://www.dropbox.com/s/pl2o5ojx4txitpv/2018-07-16_223445.png?dl=0), will the Enfold-generated thumbnails also disappear?
July 17, 2018 at 5:23 am #986250Hi,
@PierreLeBear The images are used to make a responsive site for other devices, and make the site load more effectively. Removing won’t break the site but may make your users download a very large file when looking at a thumbnail.@sckyeYes deleting a image will also delete the thumbnails.
By the way, the WordPress core also adds thumbnails in the same way.
Best regards,
MikeJuly 18, 2018 at 7:01 pm #987139Thank you very much for the clarification. It sounds like reducing the original images’ resolution when uploading them in the first place is a best practice. For most applications, a large web image can be stored in 150KB or less and still looks good. Then the resulting smaller images will require less storage as well. It’s a matter of training people who add blog posts or edit the site.
If really necessary functions.php could be edited. I try to resist these types of mods since they may be eliminated on upgrades.
PeterJuly 19, 2018 at 4:43 am #987249 -
AuthorPosts
- You must be logged in to reply to this topic.