WebP Versions Are Not Being Created

Hi David,

This is Ioanna from Imagify, and I’ll gladly assist you here!

Thank you very much for the detailed explanation through the video and for your screenshots.

Regarding the red background line that you have on the Imagify Tools page, could you please try to install and activate this helper plugin.
Once you have the above plugin activated, please check again if the error is resolved.

If not can you please check when you are on the Edit Media page(like in this screenshot) if you scroll down you will see further file info. Are there any error lines on this section?

Looking forward to your reply.

Best regards,
Ioanna

Loanna,

No change.

Requested screenshot: https://i.imgur.com/r4Z2nmO.png
Plugins: https://i.imgur.com/QORkGCf.png
New log: https://pastebin.com/4LJwqgZ7

David.

Hi David,

Thanks for your reply.

Please let me clarify that since you have the Imagify Tools helper plugin when you are on the Edit Media page and scroll down there will be the section “File Infos” as in this screenshot are there any red lines?

If so there are red lines of “File permissions” or “File owner” settings, you need to make sure that the permissions are 755 for folders and 644 for files. If it is related to the chown(File owner) settings they need to be correct so Imagify can write the newly optimized images and backup images to their proper locations on your server. It would be best to contact your host and to see if they can change your settings to allow it.

Looking forward to your reply.

Best regards,
Ioanna

Loanna,

Ahhh, yes, sorry, I didn’t see that whole section!

Updated requested screenshot: https://i.imgur.com/hBzLFs0.png

I spoke to my hosting provider and they confirmed that the server files are setup as 755 (folders) and 644 (files).

David.

Loanna,

[redacted by moderator]

David.

• This reply was modified 2 years, 8 months ago by Steven Stern (sterndata).

Hi. I have probably similar problem. I purchased from unlimited subscription and WP Rocket plugin as well. I run the optimization but the site does not show any images in WebP format and PageSpeed shows warning: Serve images in next-gen formats-. What am I doing wrong?

Hi David,

Thank you for the update.

It looks there is a red line to the File owner settings.

Can you confirm that you have checked also regarding the chown settings, ownership should be set so PHP is allowed to save files to your folders. If you’re not sure how to check this or make these changes, you can contact your host for assistance.

[redacted]

Best regards,
Ioanna

• This reply was modified 2 years, 8 months ago by Steven Stern (sterndata).

Hi all!

@tictag
Thank you very much for the ticket created. I have replied to you back.
Regarding the ownership settings, you can provide this screenshot and ask them to check if the ownership settings are correct so Imagify can write newly optimized images and backup images to their proper locations on your server. Nothing further than that.

@perties
Please see on the following link how to check if WebP images are displayed on your site https://imagify.io/documentation/how-to-check-if-webp-image-is-displayed-on-your-site/

There are a few reasons why WebP will not be displayed using picture tags:

– background images added via CSS
– there is no WebP generated
– page element HTML is loaded after Imagify looks for the source code to apply WebP markup
– images are external

There are a few main reasons for this to fail using rewrite rules:

– you are on NGINX and didn’t apply custom rules to nginx.conf file manually
– image is missing a WebP version (check by opening the image in browser and append “.webp” to its’ URL
– mod_rewrite is not active on the server (Apache)
– image is external so it can’t be rewritten

Which is the way you use to display your WebP images? If you need you can share your website URL so we can check it further.

Best regards,
Ioanna

Loanna,

Which index.php file does this error relate to? I have checked the directory the image file itself is contained in (./wp-content/uploads/2022/03/test1-scaled.jpg), and there is no index.php file in there. Traversing back, the first index.php I come across is in the ./wp-content directory and there is also one at the website root.

See screenshot: https://i.imgur.com/gjbT5UT.png

And just to your point, “so Imagify can write newly optimized images and backup images to their proper locations on your server“, the existence of test1-scaled.jpg and test.jpg in your backup folder proves that your application has the correct level of file system access. The only issue we seem to be having here is the creation of WebP format files, which is consistent with the single log failure.

David.

Hi David,

I am also replying here just in case it will help other users.

As I have replied back on our ticket communication in detail, after testing on your staging site the issue has to do with bigger WebP images after optimization.

Regarding the index.php file can be from the root, there will no be index.php in the image folder, except in wp-content/uploads. However, the red line on the file owner settings is not related.

Thank you!
Best regards,
Ioanna

For the benefit of others reading this thread, in our offline correspondence we determined that in this case the index.php error is a red-herring and the root cause was because the original image file was >2MB, which, although not mentioned anywhere in your documentation, is a limitation of the free edition of your plugin, presumably in addition to the 20MB per month total processing cap.

Original images <2MB are processed correctly.

David.

Hi David,

Thank you for the further information.
Please let me clarify regarding our documentation and the FREE plan file limitation under 2MB it is mentioned on the following link https://imagify.io/documentation/file-size-must-2mb/.

Best regards,
Ioanna

For the benefit of others reading this thread, this issue turned out to be caused by a now confirmed bug with the Imagify plugin in that, when the ‘Resize to’ option is selected, Imagify is using the original image size to assess whether the file is <2MB (restriction of the Starter Plan) and not the actual file being converted to WebP i.e. the resized image.

This has been logged in their development system here: https://github.com/wp-media/imagify-plugin/issues/521

Until this bug is resolved, original image sizes must be <2MB irrespective of how big the actual image being converted is.

David.

Hi David,

Thank you very much for providing this update! Our developers will work to get this resolved as soon as they can.

Hope you have a very nice rest of your day and weekend!

Best regards,
Joseph