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 Mar 18, 2020. It is now read-only.
I successfully installed it on a Sitecore 6.3.1 revision 110112. This module seems very powerful, but I detected a small issue related to serialization process.
When you click on "Delete obsolete version" it asks confirmation to delete all versions in the selected language. However, the serialized file contains all item languages and the serialized file is named: "Versions_
-.item".
When languages have the same number of versions, if you try to delete versions in both languages, the first file will be overwritten by the second language file.
I suggest to name the version file with the related language (i.e. for FR-FR : Versions_FR-FR_-.item and put only the related language to have light serialized files (but it will impact the revert process...)
Regards
Michael
The text was updated successfully, but these errors were encountered:
Check feedback from Marketplace below:
MICHAEL STAUDENMANN
02:56 PM on Sep 10, 2013
I successfully installed it on a Sitecore 6.3.1 revision 110112. This module seems very powerful, but I detected a small issue related to serialization process.
-.item".When you click on "Delete obsolete version" it asks confirmation to delete all versions in the selected language. However, the serialized file contains all item languages and the serialized file is named: "Versions_
When languages have the same number of versions, if you try to delete versions in both languages, the first file will be overwritten by the second language file.
I suggest to name the version file with the related language (i.e. for FR-FR : Versions_FR-FR_-.item and put only the related language to have light serialized files (but it will impact the revert process...)
Regards
Michael
The text was updated successfully, but these errors were encountered: