Allow disabling full site editing in the admin, useful to protect a production site.
Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →
WP PlugIndex currently records Disable Full Site Editing version 1.2.0 as active, updated 4mo ago and tested up to WordPress 7.0.
Allow disabling full site editing in the admin, useful to protect a production site.
A block theme will continue to work as intended on the frontend while making sure the theme can’t be messed up.
>
⚠️ Full site editing is still fresh.
For the coming months I’ll keep testing the plugin with new (beta) releases of gutenberg and WordPres.
Please contact me on the forum or on the github repository.
Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 7.0.
“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.
No tracked version or compatibility changes have been recorded by WP PlugIndex yet.
WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.
