PRO 0.2.1: Faster Scan, Playground Support, and UX Fixes
Real user feedback drives us forward. Version 0.2.1 resolves three reported issues — including a performance bug in the media library scan and a license deactivation failure in WordPress Playground.
Good feedback rarely comes from a vacuum. It comes from someone actually running the plugin — with a real media library, real requirements, and real time pressure.
Hans-Gerd Gerhards from haurand.com gave us exactly that. Three specific issues, sent directly by email. We investigated all three — and fixed two right away.
Scan Performance on Large Media Libraries
The media library scan before bulk conversion was slower than it needed to be. The cause: for every image, the plugin ran individual database queries. With 200 images, that’s 400 queries in a single request.
In 0.2.1 this works differently. Two bulk queries do what hundreds did before. The result isn’t just faster — it scales. Anyone with 1,000 images in their library will notice the difference far more than we could measure in our local environment.
License Deactivation in WordPress Playground
WordPress Playground is a browser-based WordPress environment — not a classic PHP installation, but WebAssembly running directly in the browser. HTTP requests behave differently there than on a real server: the browser steps in, and without CORS headers, it blocks the response.
This caused license activation and deactivation to time out in Playground. Eight seconds of waiting, then nothing.
The fix lives on the license server: three headers that tell the browser to allow the response through. This makes activation and deactivation in Playground just as fast as on a regular server — and older plugin versions benefit too, without needing an update.
Small UX Improvements
- Progress bar for bulk conversion updated with a new color gradient
- Grammar fix: “1 images converted” → “1 image converted”
What Happened with Bug 2
Hans-Gerd also reported a 404 error after restarting. We couldn’t reproduce it locally or in Playground — the plugin registers no custom rewrite rules that could cause a 404. We’re in contact to understand the exact context.
PRO 0.2.1 is available as an automatic update for all active licenses.