Restore Revisions
complete
Log In
James Peacock
complete
James Peacock
Hi everyone.
I'm excited to share that, thanks to feedback from our initial release of duplicating revisions, we have changed our approach when it comes to viewing and restoring content history.
The major change relates to looking at content history at the field level, and not at the item level. This allows you to view the history of individual fields, and restore content to those fields, without the need to worry about previous structure or template changes.
Of course, item level history is still possible via revision history also.
Today we have released the beta of field history to all customers. The beta includes the ability to view and restore content history for
text fields only.
Other field types will have their field history viewable upon general release next month, alongside updates to our support documentation to support the release.Please do reach out with any feedback you may have.
Thanks for your patience and continued support.
James
James Peacock
in progress
Hi everyone
I’m happy to share that work is underway to tackle one of our longest-standing feature requests. Rather than wait and release everything in one big update, we’ll be rolling out the features gradually to continuously deliver improvements related to revisions and restorations over the coming months. Whilst subject to change, this is our current approach:
- Duplicating revisions to new items:One of the simplest methods of retrieving old content is to create new items with that content. This removes the need to implement complicated structure checking/mapping to restore content. On top of that, this approach will allow you to retrieve not just old content, but old structure too. The new items created with this method will be disconnected from any templates and instead use a custom structure, allowing you to then save that structure as a new template if desired.
- Restoring content to the same item (respective of structure):The next phase will be to allow you to restore content to the same item without the need to create new items,provided the structure of the latest version and the historic version are matching.We will be keeping both methods available to you to choose from depending on your needs.
- Restoring content to the same item (irrespective of structure):The final piece of the puzzle will be to allow you to restore content to the same item regardless of the difference in structure between the latest and historic versions. For us to achieve this, additional steps will need to be undertaken by you, in the form of field mapping, to prevent any content loss during the restoration. This method means you’ll have the ability and the confidence to restore old content even when there may have been changes to templates and/or structure over an item’s lifecycle.
During the development of these features, we’ll make sure there is ample opportunity to get involved and provide feedback.
Please reach out with any questions or feedback you may have at this stage. Thank you for your patience.
Rebecca Brown
Agree! Please prioritise this fix
G
Greg Mackay
First request was made back in 2018! When is this happening?
David Campbell
planned
J
Jen Grisham
Hi there, my team is new to GatherContent and this feature is essential for a project we're working on. I can't tell if there's been any movement since November 2021, but if not, it would be huge for us. Thanks.
James Peacock
open
J
Jason Mlicki
Any update on this feature? Would definitely be valuable.
Jill Evans
Yes!!! Please, please, please do this!
Load More
→