| 开发者 | ddegner |
|---|---|
| 更新时间 | 2025年11月19日 02:12 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 6.8 |
| 版权: | GPL v2 or later |
| 版权网址: | 版权信息 |
<img> tags in <picture> with an AVIF <source> when an .avif version is present.<source> ahead of the original JPEG. Browsers that support AVIF will use it; others fall back to JPEG..avif files for existing JPEGs./wp-content/plugins/avif-local-support directory, or install via the WordPress Plugins screen.No. It creates .avif files alongside your existing JPEG originals and sizes.
If “Convert on upload” is enabled, some servers may take longer to process uploads due to AVIF generation. You can disable this and use the scheduled/background conversion instead.
Imagick is recommended for the best results and for preserving metadata and color profiles. If Imagick is not available, the plugin falls back to GD where supported.
No. The plugin does not track users or send data to external services.
On LiteSpeed/CyberPanel, the vhost sets a restrictive open_basedir (e.g., /tmp:/home/<site>). PHP’s is_executable('/usr/local/bin/magick') returns false under that restriction even when the binary exists and works from the shell. The plugin currently relies on is_executable and bails out instead of offering a fallback or a guided fix.
The plugin now estimates memory usage before processing to prevent fatal errors (crashes) on servers with limited RAM. If you see this, try switching to the "ImageMagick CLI" engine or increasing your PHP memory_limit. As a last resort, you can check "Disable memory check" in the settings to bypass this safety measure.
.avif uploads via WordPress mime filter.open_basedir causing is_executable to return false.assets/admin.js.aviflosu_* options/defines and Ddegner\\AvifLocalSupport namespaceddegner