Bender – Mosaic Image Protection

Registre de canvis

0.1.9

• Fixed the protected frame collapsing to its own aspect ratio instead of the box the theme had set: when the original <img> (or its <picture> wrapper) carried layout classes or inline styles — the common width:100%; height:100%; object-fit:cover inside a fixed-height container used by carousels, cards and hero sections — the frame that replaces it now inherits them, so the image keeps the width and height it had before.
• Fixed lazy-loading themes and plugins undoing the protection on scroll: data-src/data-srcset (and the other usual lazy-load attributes) were left on the tag, so the lazy loader put the original image URL back into src as soon as the image entered the viewport.

0.1.8

• Fixed the «Custom themes / page builders» fallback (universal_scan) leaving <picture> elements (responsive images with multiple <source> breakpoints, e.g. carousels/sliders) completely unprotected: the hi-res URLs in the <source> tags bypassed the mosaic entirely, and the generated canvas ignored the width/height intended for that layout. <picture>/<source> are now replaced by the protected frame like a plain <img>, and the frame keeps the original width/height aspect ratio when set.

0.1.7

• Fixed the «Custom themes / page builders» fallback (universal_scan, added in 0.1.6): when the only protected image on a page was reached exclusively through this fallback, the mosaic viewer script/style were enqueued too late to ever be printed (the fallback rewrites the fully-buffered page, which closes after wp_head/wp_footer already ran), so visitors saw the static low-res <img> with no <canvas> upgrade — the image looked unprotected even though the server-side markup was correct. Assets are now enqueued as soon as the fallback decides to scan the page, before output buffering starts.

0.1.6

• Added a fallback for custom-coded themes and page builders that print <img> tags outside the_content()/the_post_thumbnail() (e.g. wp_get_attachment_image() called directly, or a raw <img src="..."> in a hand-built gallery/slider): those images were left completely unprotected before, even after marking the attachment as protected. Bender now also scans the fully rendered page and swaps in the protected version for any image it recognizes. New «Custom themes / page builders» setting to disable this if not needed.

0.1.5

• Fixed 3 strings (the settings page intro and the «what it stops» note) that silently failed to load their bundled translation because the English source used a straight apostrophe (‘) while the .po files had a typographic one (’). All 6 bundled languages regenerated.

0.1.4

• Bundled ready-made translations (Italian, Spanish, French, German, Brazilian Portuguese, Chinese Simplified) in languages/, loaded automatically via load_plugin_textdomain() — no need to wait for community translations on translate.wordpress.org.

0.1.3

• All admin-facing strings (settings page, Media Library column, row/bulk actions, admin notices, error messages) are now proper English source strings wrapped for translation with the bender-mosaic-image-protection text domain, instead of hardcoded Italian. Translators can now localize the plugin via translate.wordpress.org.

0.1.2

• The fixed values of this edition (6×6 grid, watermark text/opacity, IPTC copyright/credit, 24h REST token TTL) are no longer implemented through generically-parameterized helper functions called with constant arguments. Each is now hardcoded directly inside the function that uses it (no unused $n/$opacity/$ttl-style parameters left over), so the free codebase itself contains no latent/dormant configurability for these values.

0.1.1

• All function, class, define, and option/transient names now use the bendmoim/BENDMOIM prefix (was bender/Bender, with one stray pg_rl_ transient key).
• Removed dormant Pro-only code paths from the free codebase (variable grid size, WebP/PNG atlas formats, customizable watermark/IPTC text, LSB steganographic watermark, configurable token TTL) instead of merely locking them via options. This edition now hardcodes the free-tier values described in the plugin’s own settings screen.

0.1.0

• Initial release.