Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deleted content and new content under same name/url doesn't get synced correctly #217

Open
Nuklon opened this issue Dec 1, 2023 · 1 comment

Comments

@Nuklon
Copy link

Nuklon commented Dec 1, 2023

Describe the bug
See reproduction steps.

Version (please complete the following information):

  • Umbraco Version: 13 RC3
  • uSync.Complete Version: 13 RC3

To Reproduce
Steps to reproduce the behavior:

  1. Have some content node named Test with a document type TestDoc (or something else). Make sure it exists locally and on destination server.
  2. Delete Test locally.
  3. Create a new content node named Test locally (so the url stays the same, e.g., /test/) with a different document type.
  4. Sync the Content node to destination server (... > Publish to ... > server). Use these settings:
    image
  5. On destination server, Test isn't removed and instead a new node is created named Test (1).
@jveer
Copy link

jveer commented Nov 7, 2024

This still seems to happen on 13.1.8 as well.

We have content that has been created on development and staging, with the same name/url, but a different id:

  • Development: "Test", id=1234, key=56d4edcc-c376-4b7b-baed-bb7befaa3dbb
  • Staging: "Test", id=4321, key=8fbca55f-f11d-4d55-9ebe-1c1e48b4c0f3

What I expect to happen when I sync this node from development to staging:

  1. Delete node on staging: "Test", id=4321, key=8fbca55f-f11d-4d55-9ebe-1c1e48b4c0f3
  2. Create node on staging: "Test", id=xxxx, key=56d4edcc-c376-4b7b-baed-bb7befaa3dbb

What's actually happening at the moment:

  1. Doesn't touch node on staging: "Test", id=4321, key=8fbca55f-f11d-4d55-9ebe-1c1e48b4c0f3
  2. Create node on staging: "Test (1)", id=xxxx, key=56d4edcc-c376-4b7b-baed-bb7befaa3dbb

@KevinJump do you know if there's a workaround to get this working?


Update after some more investigation:

This happened when I was importing a complete tree, so the "Test" node was actually when pushing from BBB:

  • AAA/BBB/CCC/DDD/Test

When I pushed from DDD, it did process correctly and deleted the "old" nodes, as expected.

Not sure if it's relevant, but only the DDD and it's descendants are varying by culture. AAA, BBB and CCC are not. If you need more details or examples, please let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants