Changelog

Order gets its own Sort screen; Live Draft publish fixes

Ordering moves off the post list onto a dedicated screen and stops scrambling across pages, term sorting is cut before it could mislead anyone, and publishing a Live Draft from the block editor no longer crashes the editor.

• Order — sorting moved to a screen of its own. The in-list drag handles are gone; each enabled post type gets a Sort entry in its admin menu, 100 rows at a time, saved in place without a reload. Nothing is written until you press Save.
• Order — new "Put new posts at" setting: top or bottom of the order (bottom by default). A post saved with a position of its own is left where it was put.
• Order — fixed: dragging on page 2 could overwrite page 1's positions. Positions are now absolute across the whole set. If you dragged past the first page in an earlier version, open the Sort screen and check that post type's order.
• Order — removed term sorting. Hierarchical taxonomies were never covered by the flat model, and WordPress asks for alphabetical order whenever a term list states no preference, so overriding it was inherently surprising. A saved taxonomy selection is ignored, not deleted.
• Order — the Sort screen now requires the capability to edit other users' posts; it lists every title in the set, drafts included.
• Live Draft — fixed: publishing a working copy from the block editor crashed the editor. The editor now receives the merged result and takes you to the live post, with a note that your changes were merged.
• Live Draft — the merged copy is trashed and deleted a few minutes later instead of mid-request, so an SEO plugin's metabox save moments after Publish no longer fails or drops what you typed. Restoring the trashed copy turns it back into a working copy.
• Live Draft — a stale link to a merged copy (back button, old tab) opens the live post instead of a "this item is in the Trash" error.

WordPress 7.1 compatibility

No functional change: tested against WordPress 7.1 on a real install, and the compatibility declaration says so.

First public release

Eleven features in two groups, every one of them off until you turn it on. Site Lock stops things changing behind your back; Content makes the changes you do want safe to make.

• Disable Comments — comments off everywhere, including direct POSTs to wp-comments-post.php and the REST API. Switching it on never writes to your database. Optional cleanup deletes only spam and trashed comments by default, always after showing the exact count, and excludes WooCommerce order notes, webhook logs and product reviews unless you opt in.
• Version Lock — pin a plugin to the version you tested. The pinned and latest versions both stay visible, and a probable security release is flagged rather than hidden. No plugin file is ever written, moved or deleted.
• Registration Lockdown — blocks new accounts through the form, the REST API and plugin code. Refusing administrator creation is on by default; blocking plugin-created accounts is opt-in, because it breaks WooCommerce checkout. Blocked attempts are logged.
• Installation Lockdown — freeze plugin and theme installs, uploads and updates, with an allowlist so a security plugin can keep updating itself.
• Disable XML-RPC — closes the remote write API and stops the site advertising it, including pingback.ping and system.multicall.
• Disable File Editing — removes the plugin and theme file editors, and unlike the DISALLOW_FILE_EDIT constant stays reversible from the settings screen.
• Duplicate — copy any post, page or custom post type in one click. Page builder layouts survive byte for byte, multi-value custom fields keep all values in order, and the post you copied is never modified.
• Live Draft — rewrite a published page while the published version stays up, then merge back into the same post ID at the same URL. The merge is all-or-nothing: if any part fails, the post is restored exactly as it was.
• Replace Media — swap the file behind an attachment. The same extension keeps the URL byte-identical and regenerates every registered size; a different extension tells you how many posts reference the file first, and leaves the old URL redirecting.
• Order — drag-and-drop ordering for post types and taxonomy terms, applied to your front-end queries rather than only the admin list.
• Keep URL — the two cases core’s own slug redirects skip: hierarchical post types, and posts moved to a different parent. Core handles the rest; this does not duplicate it.