An agent proposes and stops. You approve. Everything it then changes is recorded first, and any of it can be put back.<\/p>\n
Proposal.<\/strong> A run examines your site and produces a list of what it would do and why. Nothing has happened. Each finding opens to show the reasoning and the page’s current metadata.<\/p>\n Approval.<\/strong> You approve, or decline. Declining is always available, including when a licence has lapsed \u2014 you should never be unable to say no.<\/p>\n Work.<\/strong> Approved jobs queue and run in the background. Before any job touches a post, that post’s current state is recorded against the run. If that recording fails, the edit does not happen.<\/p>\n Undo.<\/strong> Restore one post, a ticked selection, or everything the run touched.<\/p>\n Restoring writes through WordPress, so every post it touches gains a revision. Undoing an agent never destroys what the agent did \u2014 both versions stay in your history.<\/p>\n The image a run chose is replaced by the one that was there before. The newer image stays in your media library; undoing an edit is not a reason to delete a file.<\/p>\n Ticking posts restores only those, filtered against what that run actually recorded. A post id from another run cannot be restored through the form.<\/p>\n A run that edited posts restores them. A run that only added rows \u2014 the librarian \u2014 has nothing to restore, so undoing it removes what it made. Those are separate buttons on purpose.<\/p>\n Revisions are a fine rollback until a site sets An agent proposes and stops. You approve. Everything it then changes is recorded first, and any of it can be put back. The path a change takes Proposal. A run examines your…<\/p>\n","protected":false},"author":0,"featured_media":0,"parent":0,"menu_order":40,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-8","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/wpcontentwriter.com\/kb\/wp-json\/wp\/v2\/pages\/8","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpcontentwriter.com\/kb\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/wpcontentwriter.com\/kb\/wp-json\/wp\/v2\/types\/page"}],"replies":[{"embeddable":true,"href":"https:\/\/wpcontentwriter.com\/kb\/wp-json\/wp\/v2\/comments?post=8"}],"version-history":[{"count":0,"href":"https:\/\/wpcontentwriter.com\/kb\/wp-json\/wp\/v2\/pages\/8\/revisions"}],"wp:attachment":[{"href":"https:\/\/wpcontentwriter.com\/kb\/wp-json\/wp\/v2\/media?parent=8"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}What undo actually does<\/h2>\n
It restores, it does not delete<\/h3>\n
It covers the featured image too<\/h3>\n
A selection is checked<\/h3>\n
Two shapes, two controls<\/h3>\n
Why not just WordPress revisions<\/h2>\n
WP_POST_REVISIONS<\/code> to false or caps it low. A restore that is only sometimes available is not a restore, so the prior state is recorded explicitly rather than assumed.<\/p>\n","protected":false},"excerpt":{"rendered":"