Content history
What it is
Version history of dynamic content. Every time content is updated, Flo saves the previous state: you can view it, restore it or delete it.
When it is visible
It is visible when history is enabled for the instance and you are editing existing content (not new content). If the feature is not enabled, the "Storico versioni" button does not appear.
Main sectors
- Fitness
- Real Estate
- Enterprise
- Customers who update existing content
Dependencies
Part of:
Can be linked to:
How it works
- Each successful save of existing content creates a version with the previous state.
- Restoring applies the chosen version and saves the current state as a new version: restoring is also reversible.
- Versions are unlimited and are deleted manually.
- The list is ordered from most recent; each entry shows version number, date, time and author.
Opening the history
- Open existing content in Dynamic content.
- Click Version history, next to Save.
- Click an entry to open the preview.
The preview is read-only and shows the version's name, description, number of media, date and author.
Restoring a version
- Open the version preview.
- Click Ripristina and confirm.
- Flo applies the version and records the previous state as a new version.
If the configuration is locked and the version renames the content item, restoring is disabled with a warning.
Deleting a version
- In the version list, click the delete icon.
- Confirm: the operation is permanent.
The other versions keep their numbering. Deleting a version frees space, because each version is a full snapshot.
What a version contains
| Element | Included |
|---|---|
| Name and description, in all languages | Yes |
| Media, order, captions and translations | Yes |
| Maximum number of visible media | Yes |
| Media and attachment files | No |
- Restoring does not re-upload files: if a media item was deleted from storage, it does not come back with the restore.
- Attachments are managed separately from the content and are not changed by the restore.
- Deleting content also deletes its history.
Configuration lock
With the configuration locked, you can only restore versions that do not change the content name. See Dynamic content.
Best practices
- Check the history before restoring: restoring creates a new version, so it remains reversible.
- Delete old and useless versions to free space.
- Use the history to understand who changed content and when.