You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 17, 2022. It is now read-only.
I'm thinking of doing a major overhaul of unversion, to make it simpler and easier to work with (and probably easier to get to core)
This requires some changes, listed below:
The config file has to go
To align with the rest of Umbraco, configuration should either be done in the UI, or by code. I'm opting for UI, with a single exception to this; adding an app setting for a default max version count across all document types.
Instead a db table will be created, containing just a document type key (the guid of the document type) and a max version count for the document type. This means that the max date difference will be removed. Also the possibility of limiting the rule to a specific xpath is gone.
Content app in the document type editor
A content app will be added to the document type editor with the ability to set a max version count for the specific document type.
This could also be injected into the permissions view, instead maybe?
A versions health check will be added
Inspired by Marc Goodson umbraco/Umbraco-CMS#9402 (comment)
This should make it possible to clear out all versions.
Version info on content info app
Version info could be injected into the info app on content nodes, displaying the current number of versions, the max number of versions allowed, and a button for cleaning up.
I would love to hear comments, suggestions etc. from people using the package. Are you going to miss something, that you just can't live without? Or do you have any other suggestions.
For a future roadmap connectors for Deploy and uSync should be added.
The text was updated successfully, but these errors were encountered:
Hi all
I'm thinking of doing a major overhaul of unversion, to make it simpler and easier to work with (and probably easier to get to core)
This requires some changes, listed below:
The config file has to go
To align with the rest of Umbraco, configuration should either be done in the UI, or by code. I'm opting for UI, with a single exception to this; adding an app setting for a default max version count across all document types.
Instead a db table will be created, containing just a document type key (the guid of the document type) and a max version count for the document type. This means that the max date difference will be removed. Also the possibility of limiting the rule to a specific xpath is gone.
Content app in the document type editor
A content app will be added to the document type editor with the ability to set a max version count for the specific document type.
This could also be injected into the permissions view, instead maybe?
A versions health check will be added
Inspired by Marc Goodson umbraco/Umbraco-CMS#9402 (comment)
This should make it possible to clear out all versions.
Version info on content info app
Version info could be injected into the info app on content nodes, displaying the current number of versions, the max number of versions allowed, and a button for cleaning up.
I would love to hear comments, suggestions etc. from people using the package. Are you going to miss something, that you just can't live without? Or do you have any other suggestions.
For a future roadmap connectors for Deploy and uSync should be added.
The text was updated successfully, but these errors were encountered: