There seems to be some strange issue when pulling and pushing content from one to another server.
I have the following scenario:
I pushed content from production to our stage server. The content was created fine on stage, except that the sorting on some of the nodes was inconsistent.
Then I go on stage and do pull on the newly created content to make sure that it is aligned with the one from production. The report says that there are lots of differences in these 2 nodes. And there shouldn't be any.
:
i think its because the parent name/alias has changed so all the nodes paths will have changes (while you see those two changes).
did you sync the parent node between the sites too ? I suspect because the parent name is diffrent it will report this as a change for all child nodes.
In most situations these two changes won't actually do anything, the path of the content item is stored in two places - one by key and one by path (you are setting the path change here).
the path change is only there incase we can't find the parent by its key. if it is found by the key the path isn't used - but here you can see if is a difference as far as the compare is concerned because the parent's name has changed.
I think , we might be able to look at removing this as a change in uSync.Complete because you would also get a change report if the key name was diffrent so if we just remove these it won't make any diffrence.
Its worth noting that when pushing/pulling content it is comparing with published versions of the page on the other server not the content saved version (this might be different).
is it possible the published parent name is diffrent even if the saved on isn't?
This is because uSync.Publisher uses the PublishedContentHandler by default (if you want it to work on Saved content you can change this to the 'standard' content handler in the uSync8.config file)
This handler works on Published content not saved content .
if you switched this out for the handler commented out below it and uSync.Publisher would be using 'saved' content.
Published content is used by default because in general you will want the published sites to look the same - i.e. don't want to get caught out by saved content leaking onto your live site.
Yes, I am only interested in moving of published content.
In my case the content I was moving was all published, that is why I experienced this issue, and to be honest I still don't understand it why is it happening.
On each server what is the name of the parent node . starting "Omdennelse IVS.." The pull indicates that this file is different between sites ?
it would seem one has (10055) in the title? and that is the change that uSync is picking up and noticing down the tree as a change (although its only a change in parent node).
Pulling inconsistency
Hi Kevin,
There seems to be some strange issue when pulling and pushing content from one to another server. I have the following scenario:
I pushed content from production to our stage server. The content was created fine on stage, except that the sorting on some of the nodes was inconsistent. Then I go on stage and do pull on the newly created content to make sure that it is aligned with the one from production. The report says that there are lots of differences in these 2 nodes. And there shouldn't be any.
:
And the details says the following:
What could be wrong here?
Regards, Vladica
Hi,
i think its because the parent name/alias has changed so all the nodes paths will have changes (while you see those two changes).
did you sync the parent node between the sites too ? I suspect because the parent name is diffrent it will report this as a change for all child nodes.
In most situations these two changes won't actually do anything, the path of the content item is stored in two places - one by key and one by path (you are setting the path change here).
the path change is only there incase we can't find the parent by its key. if it is found by the key the path isn't used - but here you can see if is a difference as far as the compare is concerned because the parent's name has changed.
I think , we might be able to look at removing this as a change in uSync.Complete because you would also get a change report if the key name was diffrent so if we just remove these it won't make any diffrence.
Hi Kevin,
Thanks for the quick reply.
That is the problem actually. No changes have been made on the parent nodes. The full path to these 2 nodes is totally equal in both servers.
I only did a fresh push and right after I went to check by pulling the same content to see if both will by in sync.
I can provide you screenshots if needed.
Regards, Vladica
Its worth noting that when pushing/pulling content it is comparing with published versions of the page on the other server not the content saved version (this might be different).
is it possible the published parent name is diffrent even if the saved on isn't?
This is because uSync.Publisher uses the PublishedContentHandler by default (if you want it to work on Saved content you can change this to the 'standard' content handler in the uSync8.config file)
Can you please instruct me on that "standard" setting how to use it as I don't see anything like that in uSync.config file.
Hi, your uSync8.config file should look something like this : https://github.com/Jumoo/uSync.Complete.Issues/blob/main/configs/uSync8.config#L22
the "default" section is the set of handlers used by the usync dashboard (with the report, import, export buttons)
the "Publisher" set is used by uSync.Publisher which is the push/pull actions in the menus.
the "Publisher" section has a content handler set to:
Published Content
This handler works on Published content not saved content . if you switched this out for the handler commented out below it and uSync.Publisher would be using 'saved' content.
Saved Content:
Published content is used by default because in general you will want the published sites to look the same - i.e. don't want to get caught out by saved content leaking onto your live site.
Yes, I am only interested in moving of published content.
In my case the content I was moving was all published, that is why I experienced this issue, and to be honest I still don't understand it why is it happening.
Hi,
On each server what is the name of the parent node . starting "Omdennelse IVS.." The pull indicates that this file is different between sites ?
it would seem one has (10055) in the title? and that is the change that uSync is picking up and noticing down the tree as a change (although its only a change in parent node).
The parent names are same on both servers.
is working on a reply...