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
Describe the bug
When we tried to push content to another server, instead create a new node, tries to update a deleted node from the target server. Also if there isn't deleted, sometimes it doesn't detect any new changes in the node between servers.
Version (please complete the following information):
Umbraco Version: 12.2.0
uSync Version: 12.1.0
uSync.Complete Version: 12.1.0
To Reproduce
Steps to reproduce the behavior:
Delete a node in the target server.
Try to push the same node with changes to the target server from another server.
See error
Expected behavior
If the node is already deleted, when you try to push the same node from another server, it should creates a new one in the target server.
Screenshots
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered:
for simplicity, we assume there is a 'source' and 'target' site
if you delete an item on your "target" site, and then publish that item from a "source" - uSync will take the deleted item and restore it to umbraco then it will publish it.
If you delete an item on stage and publish the folder the item was in, with "Delete missing items" checked, then uSync will move the item into the recycle bin on the target site. note: even if you delete an item on the source - and empty the recycle bin, on the target, usync will only even put the item into the recycle bin. this is so you can if you need to restore on the live site
if you restore an item from the recycle bin on source, it will not be published by umbraco (only moved in and saved)
if you then do a push to target there will be no changes - because uSync.Publisher only deals in published content
if you then publish the restored item and push it or its folder there should be a change and it will be pushed to target.
If you delete on source, empty recycle bin, and push - step 2 happens.
if you then create a new content item with the same name as the item you have just deleted, and push that, a new item should be created on the target site.
(so on the target site you will see the new page in the content, and the old page in the recycle bin).
this is again as intended; a deleted item will be restored if it's the same item (e.g. has the same key). but a new item with a different key, is new and created as such.
Describe the bug
When we tried to push content to another server, instead create a new node, tries to update a deleted node from the target server. Also if there isn't deleted, sometimes it doesn't detect any new changes in the node between servers.
Version (please complete the following information):
To Reproduce
Steps to reproduce the behavior:
Expected behavior
If the node is already deleted, when you try to push the same node from another server, it should creates a new one in the target server.
Screenshots
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered: