The problem is: When I have Resize larger images checked in the settings, and then also have the Disable Big Image code installed (see below), Imagify creates 2 images: an Original image file unchanged + Scaled image file that is sized as the Resize larger images max pixel size settings.
The way this should be working is: No scaled image is created and the Original image is set as the Resize larger images max pixel size settings.
Rather than the scaled image not being created and my original image being resized: The scaled image is being created using the Resize lager image max pixel settings, and the original image is being left alone. It looks like the process is REVERSED. Scaled should not be created. Original should be resized.
add_filter( 'big_image_size_threshold', '__return_false' );This is no longer working. I have tested it on a few sites. I can confirm this filter code works without Imagify and works properly with other compression plugins like Shortpixel.
]]>The upload of an image that is larger than the WP default max size is automatically scaled down to this max size (2560 px), but in lab this is not happening, and thus the original image is used, and no other resized versions are created either.
The image is uploaded, but not processed.
]]>Possibly I’m tripping this up in my process, but it is definitely a user trap if I am. Being new to WP, I simply changed the filename to what I wanted and deleted the “-scaled” suffix. WP appended the “-scaled” suffix to the saved filename, as I’ve read since I saw that that it does when the image is too wide. I wonder if I left the “-scaled” suffix on the filename if the issue might be avoided, but I haven’t tried uploaded a new file.
I’m running LocalWP, though that should not matter. The site has the following plugins:
Classic Editor
Duplicate Page
Enable Media Replace (deactivated)
Envato Market
Goodlayers Core
Goodlayers Portfolio Post Type
Location Weather
Ninja Forms
Phoenix Media Rename
Site Kit by Google
Slider Revolution
Thanks!
]]>I am doing some testing in a local environment and have a couple of questions:
We know that when a very large photo is uploaded, wordpress creates a smaller version and renames the file by adding “-scaled” to the file name, without saving the original file with the original name.
If in PODS it creates a field of type “File / Image / Video” and I insert a gallery (for example of 3 photos), when I go to extract the data in PHP with
$photos = pods_field( ‘mycpt’, $post->ID, ‘mygalleryfield’, true );
In the value [“guid”] the original filename is saved, and not the “-scaled” filename… so of course I get a 404 if I put it in the src of an image…
Does it happen to you too? Is it fixable?
]]>Why this is happening & how to remove them?. I think some images are not properly resized/compressed; thus not deleted.
Should I run the delete original option again?
]]>I have two problems:
1. The featured image does not adapt.
My images are 1920×1080 and the formula of the template is different.
I have verified that it is given the size of 1080×820 with the class=”attachment-gutenix-thumb-post size-gutenix-thumb-post wp-post-image”.
2. The cover images of the blog page. I should be able to adapt them from the size of 1920×1080. I see that scale to 720×520
I don’t know what would be the best formula to be able to correct both aspects. I know that perhaps a formula would be to be able to use images in other sizes, but I already have a website with more than 3,000 articles, which is the one I am trying to export to your template, with more than 2,000 images at 1920×1080.
Thank′s for all.
]]>