Pedro

Hello @vinodkkumar,

Thanks for reporting this, indeed it’s a bug, that notification should be dismissed. We’ll work on getting it fixed and we’ll be back here when we have a solution.

Thanks for your patience with this!

Hi Thomas,

That’s great news, thanks for the confirmation. I see that the ticket is marked as resolved, therefore I assume everything is fine now and that PHP Notice is gone for good.

Don’t hesitate to let us know if you have any other questions or concerns.

Hello Thomas,

We checked the error and it is coming from the delivery method that you chose in our plugin settings. My best guess is that you are using the PICTURE tag delivery mode, with the “Global (processes the whole output buffer before sending the HTML to the browser)” option enabled. It looks like the AMP plugin is trying to process the output buffer as well and some of our code doesn’t get executed anymore, resulting in that PHP Notice over and over again.

The potential solutions would be:

• switch to another delivery method for WebP/AVIF: either via .htaccess, or NGINX rules
• if neither of the above work, try using “Only via WordPress hooks” instead of “Global“
• check if another AMP plugin works without generating those PHP Notices
• decrease your error level to only display Warnings and Errors, and not Notices

Please tell me if any of these suggestions works for you.

Thanks!

Hello @webzunft,

I’m sorry to hear about this. To debug this further we need at least the following information:

• the full error log that you are mentioning (one entry, if all of them are identical)
• the list of active plugins & theme (or the site information taken from Tools -> Site Health -> Info)

We’ll do our best to reproduce this and check what is generating it. We do not have a direct integration with AMP plugins, but they might hook on the same hooks as our plugin and, depending on what those plugins are doing on those hooks, such logs might be generated.

Thanks, I look forward to hearing from you!

hello @kittmedia,

I’d like to follow up on this topic with a solution, which is to use the double extension for such situations. In other words, when you have a JPG named image.jpg and a PNG named image.png, the resulting WebP files would become image.jpg.webp, respectively image.png.webp. This doesn’t cause anymore the issue you pointed out and keeps the WebPs (and optionally AVIFs) separate.

You can find the constants that need to be added to your wp-config.php file to enable the double extension mode in this article from our Knowledge Base:

https://shortpixel.com/knowledge-base/article/276-list-of-constants-to-add-in-wp-config-php

Let us know if you have any other questions!

hello @servisdispleje, I will go ahead and mark this as Resolved, since we didn’t have any response. If you are still facing issues, please reply back to this thread and we’ll happily follow up. Thanks!

Hello @techwpdrift and thanks for pointing this out!

Indeed, what you are saying is supposed to be a feature, which comes into place when you have backups enabled. Its purpose is to point out the images in the Media Library that are not optimized at the current optimization level.

For some reason, it has been detected that logically they are not optimized at the same value chosen after the update in the selector. This is an issue because I might want to optimize new images to Balanced from now on but keep the old ones at a quality level of 90, for example.

You should be able to do that, unless you plan on running a bulk optimize or manually click on the Optimize Now button.

I would like to know if it is possible to choose a quality level with your new selector that does not affect the images that were already optimized previously and does not affect the count of those remaining to be optimized.

This is possible using the filter that was added with this change in the settings, for this kind of situations. In short, you can add this line of code either in your theme’s functions.php file, or by using a plugin such as Code Snippets (please replace 90 with the value you used to have before choosing the new option):

add_filter( 'resmushit_image_quality', function() { return 90; } );

Please tell me if you have any other questions!

Hello @po64,

Here’s how you can use the filter we have recently introduced in our plugin. You need to add the following line to your theme’s functions.php file, or by using a plugin like Code Snippets:

add_filter( 'resmushit_image_quality', function() { return 90; } );

Feel free to change 90 to a quality level suitable to your needs.

Best wishes!

To follow up on this, we added the necessary integration in version 5.6.1 of our plugin and from this version on, all images uploaded via Formidable Forms (as described above) are optimized directly in the Media Library, with no more 404s. The “frm_file” requests were actually coming from the protection that Formidable Forms adds to the uploads and this is also handled correctly now by the integration added.

@askwpgirl can you please confirm that everything works as expected now? Thanks for reporting this!

Hello @jumper,

First of all I want to ensure you’re posting the question to the right plugin ?? Our ShortPixel Image Optimizer plugin isn’t doing any kind of lazy loading, therefore I’m a bit confused.

If you are using the PICTURE tag delivery method for WebP/AVIF files delivery, this may indeed interfere with various lazy loading mechanisms and compatibility issues may arise (this is a rather known limitation of the PICTURE tag method).

If you could give us a more specific example of a link where you are using the data-skip-lazy attribute, combined with our plugin, we can have a look and see what can be done about it.

Thanks!

hello @deargeek,

Thanks for pointing this out, version 5.6.2, just released, contains a fix for this.

All the best!

Hello @servisdispleje,

After updating to the current version, it reports that it does not have access to .htaccess and compression does not work.

From this perspective, version 5.6.0 should not have changed anything related to the .htaccess file & access, are you sure the file is writable on your hosting setup and nothing changed in your server configs? It would help if you could provide us with your site information, if possible (from Tools -> Site Health -> Info -> Copy site info to clipboard).

For the optimization message, can you please include the file name as well, if possible? What kind of files are those?

version 5.4.3. works normally

The previous version before 5.6.0 was 5.5.5, does that one work correctly?

Thanks!

Thanks for the confirmation @mathieu! Version 5.6.1 is planned for next week, I hope that’s ok ??

Hello @mathieu,

Can you please check if the version below fixes the error you described?

https://shortpixel.com/downloads/shortpixel-image-optimiser-5.6.1-DEV02.zip

Thanks, I look forward to getting your confirmation about this!

All the best,

And just to add some details, the errors were generated by what we call “Silent Mode” where the plugin doesn’t display any notifications at all. When that mode was enabled by its constant, some checks were missing and we added them in version 5.6.0.

Thanks @tatof for reporting and helping us in getting it resolved!