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
In case anyone else has this problem, there might be a workaround. It is not the best thing to do, especially when you have big projects with a lot of changes in your workspaces. So be aware, that:
This might lead to loss of data, so always back up your files!
I found out that there are two objects when I search for the ID 000481bc-64c6-4579-afb9-d7fb6534295e from the above error message. I found both of them in the neos_contentrepository_domain_model_nodedata table. In the column removed, one had the value 0 the other one 1. When I wanted to remove the entry with removed = 1, I noticed that there are way more entries that share the same behavior, so I run this command in phpMyAdmin under the SQL tab of the neos_contentrepository_domain_model_nodedata table:
DELETE FROM neos_contentrepository_domain_model_nodedata WHERE removed = 1;
After that I could run node:repair but also the workspace:publish task without any problems.
Is there an existing issue for this?
Current Behavior
When trying to publish a workspace (neue-navigation-udzay) to live, I get the following error:
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry error.
When I try to run ./flow node:repair --workspace neue-navigation-udzay I also get the following error message:
Expected Behavior
Workspaces can be published to Live and duplicate entries like this are resolved on their own.
Steps To Reproduce
No response
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: