Open Nuklon opened 11 months ago
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:
56d4edcc-c376-4b7b-baed-bb7befaa3dbb
8fbca55f-f11d-4d55-9ebe-1c1e48b4c0f3
What I expect to happen when I sync this node from development to staging:
8fbca55f-f11d-4d55-9ebe-1c1e48b4c0f3
56d4edcc-c376-4b7b-baed-bb7befaa3dbb
What's actually happening at the moment:
8fbca55f-f11d-4d55-9ebe-1c1e48b4c0f3
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.
Describe the bug See reproduction steps.
Version (please complete the following information):
To Reproduce Steps to reproduce the behavior: