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
Hi @Gnome and welcome to Backdrop When I create custom layout templates I put them in /layouts/custom/my_layout Note: you can split modules and layouts between contrib and custom...
My layout template (layout--blog.tpl.php) doesn't work
This post explains how to do this in Drupal 7. In Backdrop, File Entity is already part of core. You will need to download and install module Views Field View. https://drupal.stackexchange...
I Need to Display an Image in a View that was Uploaded to a Webform
After alot of trials, i have done the obvious and translated the whole block for different languages with each property condition as follows: ->propertyCondition('langcode', 'en...
How to get the current page language?
Thanks so much! It's working now: I was able to transfer the docroot files to the containing directory without the need for a second database or any manual configuration export/import/sync...
Backup & Migrate Config: There was a problem creating field...database table with the name already exists.
Ah, I see. Sorry, I hadn't clicked the link and assumed it was the instructions for upgrading from Drupal 7. If you are simply copying a site from one location on a server to another, the...
Backup & Migrate Config: There was a problem creating field...database table with the name already exists.