I've been experimenting with Usync ContentEdition to synchronize page content between two Umbraco installations. For the most part, it works but I've noticed a strange tendency for Usync to rather the updating the existing pages, duplicating the entire page tree.
See below images for examples:
SiteA (Empty Umbraco Site express installation with the Fanoe theme)
SiteB after import from SiteA (Dito)
As you can see, Usync has created a new top node "Home (1)".
What causes this behavior? Is it only after forcing a complete import that this can happen (i don't remember doing it but I suppose it is possible).
Note that the property ID is the same on both sites.
yes this is currently the default behavior if the target content has not been brought across by usync.
when usync does the import it tries to match by internal id (the guid below the id) if this doesn't match it will create a new content item.
if both sides of your tree have content before usync is ran, then the guid's will be diffrent and the content won't match - under those circumstances usync will create new content (and you will get your duplicate).
older versions of usync did this by name not guid - but it was slower and it's much more likely to go wrong later on (if for example you rename a node - then we can no longer find it).
I am experimenting with putting some fallback stuff in - so if the guid isn't found we will look at the level we are at for the node with a name of a certain content type - I need to check this works and isn't slow because it will hit the database a lot more than the current import does.
The latest release of uSync has gone out today (v3.3.1) and it contains the fixes for this.
PM> update-package uSync
or download the package from our
Should apply the changes and the dashboard should report v3.3.1 and (5.6.1 for core).
This will fix the content import so that duplicate nodes are not created when you import content to an existing site.
usync now matches content on both name and content type - so if the target site has diffrent content types then you are still going to get duplicates - but that shouldn't be an issue for most people
Usync ContentEdition creating new page root duplicates
I've been experimenting with Usync ContentEdition to synchronize page content between two Umbraco installations. For the most part, it works but I've noticed a strange tendency for Usync to rather the updating the existing pages, duplicating the entire page tree.
See below images for examples:
SiteA (Empty Umbraco Site express installation with the Fanoe theme)
SiteB after import from SiteA (Dito)
As you can see, Usync has created a new top node "Home (1)". What causes this behavior? Is it only after forcing a complete import that this can happen (i don't remember doing it but I suppose it is possible).
Note that the property ID is the same on both sites.
Hi
yes this is currently the default behavior if the target content has not been brought across by usync.
when usync does the import it tries to match by internal id (the guid below the id) if this doesn't match it will create a new content item.
if both sides of your tree have content before usync is ran, then the guid's will be diffrent and the content won't match - under those circumstances usync will create new content (and you will get your duplicate).
older versions of usync did this by name not guid - but it was slower and it's much more likely to go wrong later on (if for example you rename a node - then we can no longer find it).
I am experimenting with putting some fallback stuff in - so if the guid isn't found we will look at the level we are at for the node with a name of a certain content type - I need to check this works and isn't slow because it will hit the database a lot more than the current import does.
Kevin
Hi
to follow up - I have added some code to do a legacy look up when content is imported and we can't find it.
this also highlighted a bug with content lower down the tree not always coming in correctly - so I've addressed that too.
https://github.com/KevinJump/uSync/issues/112
it will be in the next patch release for content edtion (soon once i've done testing)
Hi
The latest release of uSync has gone out today (v3.3.1) and it contains the fixes for this.
or download the package from our
Should apply the changes and the dashboard should report v3.3.1 and (5.6.1 for core).
This will fix the content import so that duplicate nodes are not created when you import content to an existing site.
usync now matches content on both name and content type - so if the target site has diffrent content types then you are still going to get duplicates - but that shouldn't be an issue for most people
Thanks, we'll check it out!
is working on a reply...