Fmtify: Auto WebP and AVIF Converter

1.3.0

• Added: Image Engine setting on the main settings page (Auto / GD faster / Imagick better quality, slower). It replaces the per-run Backend selector on the Bulk Convert page and now applies to ALL conversions: uploads, Bulk Convert, and WP-CLI. Auto keeps the previous behavior (GD first, Imagick fallback). When the selected engine is unavailable or cannot produce a format, Fmtify falls back automatically.
• Fixed: Every GIF (and PNG-8 / indexed BMP) failed on the GD engine with “Palette image not supported by webp” and “avif doesn’t support palette images” warnings. GD loads these as palette images; they are now converted to truecolor before encoding, preserving transparency.
• Fixed: BMP images always failed on the GD engine because the BMP loader was missing.
• Fixed: Static thumbnails of an animated GIF are now converted; the animated files themselves are excluded up front instead of being counted as conversion issues and retried on every bulk run.
• Improved: More precise animated GIF detection (anchored frame headers, fewer false positives from pixel data).
• Improved: Engine availability probes now run once per request instead of once per converted file.

1.2.15

• Fixed: Bulk Convert could report 100% complete while leaving most of the library unconverted. The fresh-pass query window did not advance past images that stay in the result set (failed, missing on disk, excluded type, or any image when conversion tracking is off), so each batch re-read the same items. The query now paginates with a persistent offset in all modes and orders by ID for deterministic batches.
• Fixed: An image was marked as fully converted when only some of its sizes succeeded. The _fmtify_converted meta now records a format only when every file (original plus all thumbnails) converted, so a later fresh pass retries partially failed images. Applies to upload conversion, Bulk Convert, and WP-CLI.
• Fixed: The PHP-fallback rewrite rule was registered only during activation, so saving permalinks (or any plugin flushing rewrite rules) silently removed it. The rule is now registered on every request and self-heals after plugin updates.
• Fixed: Requests for missing images could render the homepage with HTTP 200 instead of returning a 404 when serving via .htaccess. The image handler is now active for every serving method and sends a real 404 for missing files.
• Fixed: The rewrite rule assumed uploads live at wp-content/uploads under the site root. The pattern is now derived from the actual uploads URL, supporting subdirectory installs, the UPLOADS constant, and multisite upload paths.
• Fixed: The Imagick backend reported success when it wrote a 0-byte file (for example on an unwritable directory). It now removes the empty file and reports the failure, matching the GD backend.
• Fixed: Serving an original PNG, GIF, or BMP through the PHP fallback could send Content-Type: image/jpeg when MIME detection failed. The type is now derived from the file extension.
• Fixed: Animated GIFs were silently flattened to a static first frame. They are now detected and skipped so the animation is preserved.
• Fixed: wp fmtify bulk loaded every attachment ID into memory at once and could exhaust memory on large libraries. It now pages through the library 100 attachments at a time.
• Fixed: The “Conversion issues” counter could exceed the total because it counted every failed file and format. It now counts each image once.
• Fixed: Conversion stats counted files that had failed. The total now reflects actual successful conversions.
• Fixed: Bulk job progress and lock transients are now removed on uninstall.
• Changed: The PHP image handler refuses to serve anything but the supported image extensions, even if the query variables are set directly.
• Changed: Removed unused internal converter methods and an unused setting key left over from an earlier architecture.

1.2.14

• Fixed: register_setting() sanitize_callback was an instance method reference ([$obj, ‘sanitize’]) that WP Plugin Check cannot resolve statically, causing a false “missing sanitize_callback” warning. Fmtify_Settings::sanitize() is now a static method registered as [Fmtify_Settings::class, ‘sanitize’], which is fully statically-analysable.
• Hardened: sanitize() now accepts mixed input — previously the array type hint would throw a PHP TypeError if WordPress called the callback with a non-array value (e.g. null on a fresh install).

1.2.13

• Performance: .htaccess active state is now cached in a WordPress option (fmtify_htaccess_active). Previously Fmtify read .htaccess from disk on every front-end request (in auto serving mode) to decide whether the PHP image handler should register. The option is kept in sync whenever rules are written or removed.
• Performance: Fmtify_Compatibility::get_status() result is now cached in a transient for one hour. Previously the full server-probe (including two Imagick::queryFormats() calls) ran on every admin page render.
• Fixed: is_path_in_uploads() path-prefix check now appends a trailing slash to both sides of the comparison, preventing false positives for sibling directories such as uploads_backup/ or uploads-old/.
• Fixed: Canonical list of convertible source MIME types is now defined once in Fmtify_File_Helper::CONVERTIBLE_MIME (jpeg/png/gif/bmp) and referenced by all conversion paths — upload hooks, bulk processor, and CLI. Previously the upload hook silently accepted image/tiff (never served by the rewrite rules) and image/webp (already a modern format; no sidecar needed).

1.2.12

• Fixed: readme.txt had duplicate == Upgrade Notice == headers causing the WP Plugin Check 300-character limit warning. Merged all version entries under one header.
• Fixed: set_time_limit() in the AJAX batch handler now suppresses the Plugin Check discouraged-function warning via phpcs:ignore. The call is intentional.

1.2.11

• Updated translations for all 8 bundled locales (de_DE, fr_FR, ja, pt_PT, ru_RU, fa_IR, vi, si_LK) to cover new strings added in 1.2.8 and 1.2.9: Strip metadata, Conversion tracking, Backend selector, and related UI descriptions.