Is there a way through the UI or at the folder level of umbraco 7 that administrators can delete all past versions for content nodes without installing a package like unversion?
My concern with unversion is the possibility of connection leak issues. I am not sure how much weight that has in impacting either the user or the CMS itself.
There isn't a way via the cms itself to clear the version history on a specific node or section - although it would be a great option to have!
or even a 'health check' option in the developer section.
UnVersion therefore has been around for a long time, clearing version history based on some configuration settings, eg how many versions to keep / how long to keep them for.
If your concerned that UnVersion is running in the background, then all it is doing is running a set of SQL scripts based on the configuration options, and you could run these manually against the database yourself, alot depends on whether you have versions that have built up over time, so running the scripts manually ever three months would be fine, or whether you are creating 30 versions a day, and it's building up horribly quickly.
You can see the code here for unversion on github:
delete all past versions
Is there a way through the UI or at the folder level of umbraco 7 that administrators can delete all past versions for content nodes without installing a package like unversion?
My concern with unversion is the possibility of connection leak issues. I am not sure how much weight that has in impacting either the user or the CMS itself.
Thanks
Hi blackhawk
There isn't a way via the cms itself to clear the version history on a specific node or section - although it would be a great option to have!
or even a 'health check' option in the developer section.
UnVersion therefore has been around for a long time, clearing version history based on some configuration settings, eg how many versions to keep / how long to keep them for.
If your concerned that UnVersion is running in the background, then all it is doing is running a set of SQL scripts based on the configuration options, and you could run these manually against the database yourself, alot depends on whether you have versions that have built up over time, so running the scripts manually ever three months would be fine, or whether you are creating 30 versions a day, and it's building up horribly quickly.
You can see the code here for unversion on github:
https://github.com/umco/umbraco-unversion/blob/develop/src/Our.Umbraco.UnVersion/Services/UnVersionService.cs
and see how the connection to the database is being opened, (and closed!!!) and the sql it generates.
regards
Marc
Thank you Marc for the rich response. This helps me understand where we are at with things and what to use. Appreciate it.
is working on a reply...