-
Notifications
You must be signed in to change notification settings - Fork 638
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
Duplicating Entry Doesn't Create a Unique UID #4653
Comments
"Save as New Entry" does the same thing. We end up with two elements that have the same UID. |
I had noticed this bug during 3.2 development, but thought it was limited to 3.2 alpha releases, so while 3.2 has a migration to fix duplicate UIDs, it only runs if you’re coming from 3.2.0-alpha.6 or later. So I just added a new console command that you will be able to run once Craft 3.2.8 is released, which will run the same migration code. ./craft utils/fix-element-uids To get the fix early, change your "require": {
"craftcms/cms": "dev-develop#0e0c89e4684e07d784a1e4d5bdcaa3395ee07a54 as 3.2.7",
"...": "..."
} Then run |
Closes craftcms#4653 for the 3.1 branch.
We are unable to upgrade to 3.2 right now. I submitted a PR for 3.1. |
We aren’t releasing additional 3.1 releases. You’ll just have to point composer.json to your fork with the fix, until you are ready to update to 3.2. |
@brandonkelly, this is a critical bug, hopefully you'll reconsider implementing some fix for this on |
Craft 3.1 isn’t an LTS release. As said you are welcome to use a fork with your own fix until you’re ready to update to 3.2. |
Closes craftcms#4653 for the 3.1 branch.
Description
When you select an Entry and choose "Duplicate" from the action menu, it creates a new entry with the same UID.
Steps to reproduce
This query shows current duplicates in the database:
Additional info
The text was updated successfully, but these errors were encountered: