Know which plugins and theme code break in the iframed post editor before you update. Ready, Check or Likely broken, per plugin, with file and line.
From WordPress 7.1 the post editor always renders its canvas inside an iframe, list tables use new row markup, and several component props no longer do anything. Plugin and theme code written for the old editor keeps working right up to the update, and then a meta box disappears or a custom panel renders empty.
It checks a live site and gives every installed plugin and the active theme one of three verdicts: Ready, Check or Likely broken. Each finding names the file and line (or the callback that renders a meta box), a severity, a confidence level, why it matters, how to fix it, and a link to the official developer note.
document or jQueryapiVersion below 3 and props that changed in 7.1The scan is read-only. It never touches other plugins’ files, posts or settings, and scan data never leaves your site.
Agencies that maintain many client sites and need a go/no-go before a major WordPress update, and site owners who want to know what to test, and which vendor to contact, before they click Update. It is a readiness report for the people who run the site, not a developer linting tool.
wp editor-readiness scan --fail-on=broken.Ready, Check or Likely broken for every plugin and the active theme, with severity and confidence.
Each finding names the file and line, why it matters, how to fix it, and the official dev note.
Opens each post type editor in a simulated state and records every meta box, script and style it loads.
Lists every meta box per post type and whether it would turn off real-time collaboration.
Export a print-friendly report for clients; a white-label setting removes the plugin name.
wp editor-readiness scan with --fail-on=broken for scripted pre-update checks.
Every plan comes with the full plugin, a license key the moment you pay, and updates and support while your license is active.
Black Friday Sale
First year at the offer price, then $29/yr.
First year at the offer price, then $59/yr.
First year at the offer price, then $119/yr.
One payment, yours forever.
What Editor Readiness Scanner needs to run, and what it works with.
Since WordPress 7.1 the post editor always renders the content canvas inside an iframe, a separate document from the admin page. Editor scripts that query the global document, or stylesheets enqueued only on the admin page, no longer reach the canvas. The scanner finds that code before you update.
No. The scan is read-only. It never edits other plugins' files, posts or settings, and stores only its own scan results and settings. Scan data never leaves your site; the only outbound requests are the license and update checks to technoleet.dev. The runtime check does run other plugins' editor code, exactly as opening the editor would, so run the first scan on a staging copy if you can.
On demand. Click Run scan under Tools → Editor Readiness, or run wp editor-readiness scan from WP-CLI. The scan runs in short chunks while the page is open and continues in the background through Action Scheduler or WP-Cron if you close it. New rules for new WordPress releases arrive as plugin updates; re-run the scan after updating.
Install the plugin from your technoleet.dev account zip, activate it under Plugins, then go to Tools → Editor Readiness License, paste your key and click Activate License. Updates then appear on Dashboard → Updates like any other plugin. To move the license, deactivate it on the old site first.
The plugin keeps scanning. Automatic updates, new rule entries and support stop until you renew. If technoleet.dev cannot be reached, a previously valid license keeps working for 14 days.
Support is included with an active license for one year and is handled through your technoleet.dev account. Include the JSON export of your scan when you write in; it has everything we need to reproduce a finding.
Pay once a year, get your license key instantly, and install it in a minute. Updates and support are included.