ddur

@deksar

Looks like FreeBSD is an exception, ImageMagick library v7 is not available from Debian 10 repository at all. Debian php8.0-imagick is compiled/linked with ImageMagick-common v6.9.10.23

I guess you are the only one using ImageMagick-common v7 along with Warp iMagick.

ImageMagick-common v7 will be allowed from Warp iMagick 1.9.4.

And the plugin is working great.

You could use that sentence as a Recommendation.

@deksar

Because ImageMagick library version 7 is not by default installed, and consequently not tested in our testing environment (Debian 10).

I you can confirm that plugin (1.9.2) is working properly with ImageMagick library 7, please let us know so limitation can be removed by next release.

Thanks for reporting.

BTW, What is OS (Linux?) distribution and version you use?

Hi @hakkanirudha,

It is possible and idea was already evaluated, but since every new update of core, plugin or theme would undo/overwrite such optimization, new optimization would be required after every core/plugin/theme update. Handling such events would be largely out of scope of this plugin functionality but that idea will be considered for implementation in the future, as new plugin or plugin extension.

Thanks for asking.

Actually, I was checking another function.

On line 2079, replace $tab_index = 0, with $tab_index,.
That will remove the warning.

Regardless of warning, plugin/function works correct as $tab_index argument is not optional at all.

Thanks for reporting.

I know, that is false warning, there is no optional parameter there.
Warning will probably be fixed in some future PHP8 release.
Just ignore.

@stephenhampton

As far as I know, A2 Optimize IS A CACHING PLUGIN.

@mindas22

Sure, there is a link in settings page help:

Recipe: serve WebP with nginx conditionally

If you use WordOps, that is already configured.

??

@mtjr

I can’t find that message (or parts of, like “refresh page”) anywhere in my WordPress installation (code). I guess, that message is generated from some other plugin you have.

If you can, please try to search for that message in your WordPress install directory files.

If you have new/fresh WordPress installation, you may install warp-imagick plugin to confirm that it works there (it should as other 10.000 installs do).

If you can’t do any of above, then start disabling other plugins until you find one to blame.

@mtjr

Sorry, I can’t reproduce that error.

Maybe your session has expired? Go back to settings page, reload page and try to save again.

Are you logged in as administrator?

@waltercruz

Issue concerning WP_CLI media regenerate may be resolved and fixed in next update release.

Thanks for reporting

@waltercruz

Looks like this plugin or WP-CLI media regenerate code has recently changed in incompatible way. There is currently nothing that can be done in this plugin. Support for WP-CLI media regenerate will be probably dropped.

@waltercruz

Through WP CLI no webp is generated, but when I use the Regenerate Thumbnails Plugin, the webp files are created.

Maybe your php-cli (it is in separated installation/directory!) has no php-gd extension installed? As far as I know, Regenerate Thumbnails plugin shares the code from “WP CLI media regenerate” command.

Please let me know if that is the case.

@waltercruz

WP CLI is not triggering the warp plugin – it only works from interface – using the regenerate thumbnails.

How do you know that?