We just added a new term to an existing taxonomy vocabulary, which worked fine. But when I go to the "list terms" page and try to move the new term to a different place within the list (keeping the same parent term), I get this error when I try to save it:
Error
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '33-31' for key 'PRIMARY': UPDATE {taxonomy_term_hierarchy} SET `parent`=:db_update_placeholder_0 WHERE (`tid` = :db_condition_placeholder_0) ; Array ( [:db_update_placeholder_0] => 31 [:db_condition_placeholder_0] => 33 )
Also, when I reload the "List terms" page, the parent term was displayed in a different place.
Oh, and the terms that it's complaining about weren't touched in the editing.
I am running the latest version of Backdrop (1.31.0) and all modules.
Any idea what's going on?
Recent comments
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists
Thanks, I have to go out now, I will try later on and report back
Importing the staged config throws an error: another field with the same name already exists
Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....
Importing the staged config throws an error: another field with the same name already exists
Hi @yorkshirepudding! Nothing in admin/reports/fields or admin/config/development/configuration/single/export There is a field in the database though. Should I just copy the item...
Importing the staged config throws an error: another field with the same name already exists
That is not a core field so my guess is it must exist, though perhaps it is a field defined but without any instances. A few places to check: admin/reports/fields - is it...
Importing the staged config throws an error: another field with the same name already exists