Revisions Pro

v4.0.0

5 days ago

1. • Revisions Pro 4.0 needs Grav 2.2.15 or later, API 1.1.3 or later and Admin 2 2.2.3 or later. Sites still on Grav 1.7 should stay on Revisions Pro 3.0.
   • New Page Revision Storage option. storage: data keeps page revisions in user/data/revisions instead of next to each page file, filed under a permanent id Grav writes into each page folder (.page-id), so a page's history follows it when its folder is renamed, reordered, moved in Admin 2 or moved with git or FTP, and survives the page being deleted. The default, storage: page, keeps revisions next to the page files as before.
   • Deleting one translation of a page in Admin 2 now keeps it in the trash, listed as "German translation of Pricing" next to deleted pages, and restoring it puts the file back into the page, even if the page's folder was renamed or moved since. In storage: data the translation's history stays listed after the delete, ending with a revision marked Deleted.
   • Pages deleted in Admin 2, one at a time or several at once, now go into the trash. Restoring one in storage: data brings its history back with it.
   • Trash page in Admin 2: a Trash item at the bottom of the sidebar, above Settings, with a live count, lists everything in the trash, whole pages and single translations, with restore, permanent delete and Empty trash, filters for pages, translations and language, and a search by title, address or file. The trash button in the Revision History panel stays as a shortcut and shows the same list.
   • Preview an item in the trash without restoring it, on the Trash page and in the Revision History panel's trash view: a deleted translation shows its file, a deleted page shows every language file it held (default language first, with a language switcher), its media with image thumbnails and its child pages. Each file shows its first 200 KB, with a note when it is longer, and the preview can restore the item.
   • The page title of a deleted translation in the trash links to the page in the editor, opened in the deleted language, so you see the page the translation belonged to and can create the translation again. The link follows the page if its folder was renamed or moved since, and isn't shown when the page is gone or you can't read it.
   • Undo a delete: right after deleting a page or a translation in Admin 2, the toast has an Undo button that restores it from the trash, and the delete confirmation says the page can be restored from Trash instead of "This cannot be undone".
   • New bin/plugin revisions-pro page-ids command gives every page folder its id, and with --migrate moves existing page revisions out of the page folders into user/data, keeping their dates. Running it again changes nothing.
2. • With storage: data, page folders hold no revision files, so a site that commits user/ to git (or syncs it) no longer picks up a .rev file on every save. Ignore /data/revisions and commit the .page-id files.
   • Restoring a page revision in storage: data first keeps the current content as a revision, and the history marks restored and deleted revisions.
   • A copy of a page starts its own history instead of sharing the original's.
   • Restoring a deleted page refuses with a clear message when another page now uses its address or the folder it was in is gone, instead of overwriting or recreating anything.
   • A restored page's child pages get their page ids back, so their histories reconnect too.
   • A delete in Admin 2 that can't keep the page in the trash is stopped, with an error, instead of deleting the page with nothing kept. A delete that fails after it was kept leaves no trash item and no "Deleted" revision behind.
   • Two saves of one page at the same moment no longer lose each other's history entry, and two deletes or restores at once no longer lose an item from the trash list.
   • The trash list, its count and Empty Trash only take in the items the signed-in user could restore.
   • In the revisions panel the Empty Trash button sits in the trash view's header, out of the bottom corner where a site's floating buttons could cover it, and its dialogs can be used with a keyboard and a screen reader.
3. • [security] Restoring a page from the trash to a custom location accepted a folder name such as ../../config, which could write, and with Overwrite delete, folders outside user/pages. Folder names, slugs and parent routes are now single names, the target must be inside the pages folder, and trash item ids are checked.
   • [security] Images, videos, PDFs and other media in a deleted page kept in the trash could be downloaded directly from the site by anyone who knew or guessed the address of the trash item, because Grav lets the web server hand out media files under user/data. Files in the trash are now stored with a .trashed ending, so the web server refuses them, and restoring puts the original names back. Items already in the trash are renamed the first time the trash is opened or listed.
   • [security] Revision and trash endpoints now check the same permissions as the API's pages and config endpoints, including a page's own permissions frontmatter. Before, any signed-in user could list revisions, api.pages.read was enough to read the raw content of configuration revisions, and editors with api.pages.write could not restore revisions at all. Configuration revisions now need api.config.read to list and api.config.write to view or restore.
   • Revision dates in the Admin 2 panel show in your own time zone. They were the server's time read as yours, so a revision saved at 11:57 AM could show as 5:57 PM.
   • Restoring a translation, or a revision, writes into the page's current file for that language, so a page whose template changed since (default to item), or whose default language moved between default.md and default.en.md, no longer ends up with two files for one language.
   • The daily cleanup also removes old configuration revisions on a site where no page revision was ever saved to the old revisions index (any storage: data site); it used to stop without removing anything there.
   • Languages with a region, such as en-us, pt-br or es-us, are now recognised everywhere, so revisions of those pages list, compare and restore correctly.
   • Restoring a revision of a translation writes that translation's file, instead of possibly the page in the site's default language.

v3.0.4

3 weeks ago

1. • Restoring a configuration revision saved in Admin 2 now puts back only what that file held, instead of copying every setting into it, which could make an environment's settings hide later changes to the main configuration.
   • Comparing a configuration revision with the current version in Admin 2 no longer shows every default setting as a change.
   • Saving configuration without changing anything no longer adds a duplicate revision when an environment folder exists.
   • In Admin 2 the revisions panel now lists, compares and restores the revisions of the environment picked in the environment selector (with API plugin 1.0.50 or later).

v3.0.3

2 months ago

1. • Installing or updating on Grav 2 no longer fails on a dependency that cannot exist there. The plugin still asked for the Grav 1.7 admin plugin, so bin/gpm install stopped with a PHP error, and the Plugins page reported a failed update. On the testing release channel it could go further and install the old admin plugin alongside Admin 2 getgrav/grav-premium-issues#618

v3.0.2

3 months ago

1. • Fixed "No valid authentication credentials provided" errors in the admin revisions panel on some hosting setups.

v3.0.1

6 months ago

1. • Fixed 500 error on the revisions diff endpoint caused by a missing required argument when constructing the diff engine.

v3.0.0

6 months ago

1. • New Grav 2.0 + API + Admin 2.0 support

v2.0.0

1 year ago

1. • Added recoverable Trash workspace for deleted pages, including restore/overwrite workflows and configurable retention.
   • Introduced toolbar trash badge and dedicated panel for listing, restoring, and purging deleted pages.
2. • Extended configuration/translation options to manage trash retention limits and disable the feature when not needed.

v1.0.0

1 year ago

1. • Initial Release...