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
When using clones in Sitecore, you will experience that the links between the clones are not persisted when deserializing items into Sitecore again, hence clone notifications no longer work.
This has been documented in the support database.
The solution to this is simply to rebuild the link database.
A simple - Globals.LinkDatabase.Rebuild(database); would propably solve the problem.
You could consider adding a setting to the serialization.config, that allows you to do a rebuild of the links database upon a successfull Unicorn sync.
The text was updated successfully, but these errors were encountered:
Rebuilding the links database can take a very long time if the database has very many items in it so I do not see this likely being a default behavior.
My guess as to why the links are not persisting is because deserialization is normally run under the context of an EventDisabler to improve loading speed (this is true of both Unicorn and Sitecore serialization).
If you want to see if it helps, install Unicorn from source and take a look at SerializationLoader.cs line 62. If you remove that EventDisabler, you may see link database updates persist and thus your clones keep their links.
If that solves your problem I will be happy to make disabling that option a configurable piece of Unicorn for people that use clones.
Hey
Very good work on Unicorn.
You could consider the following improvement.
When using clones in Sitecore, you will experience that the links between the clones are not persisted when deserializing items into Sitecore again, hence clone notifications no longer work.
This has been documented in the support database.
The solution to this is simply to rebuild the link database.
A simple - Globals.LinkDatabase.Rebuild(database); would propably solve the problem.
You could consider adding a setting to the serialization.config, that allows you to do a rebuild of the links database upon a successfull Unicorn sync.
The text was updated successfully, but these errors were encountered: