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
Clone region copies page tree id instead of assigning a new one #1259
Comments
It seems that all translations are fully redundant for the duplicate pages. That means we can probably just delete one page and all of its translations. The same is happening in the test CMS with the following tree IDs: 160, 357, 358, 165, 168, 163, 158, 165 |
I could reproduce this locally on develop. Duplicating a region causes duplicate tree ids for different trees of different regions, because the pages are just copied without the value of the |
Add test case which fails in the current state to reproduce #1259
- Add test case which fails in the current state to reproduce #1259 - Order translation models by language to keep deterministic order to compare querysets
- Add test case which fails in the current state to reproduce #1259 - Order translation models by language to keep deterministic order to compare querysets
Describe the Bug
After duplicating a region, the page tree is copied but the tree_id for the new region is keeping the same value as the original tree.
Other tree IDs with 2 root pages: 236, 230, 238, 234
Expected Behavior
Only one root page per tree.
Additional Information
This is a remant of the migration.
The text was updated successfully, but these errors were encountered: