Dragging and dropping taxonomy terms clears out Breadcrumb paths
| Project: | Taxonomy Breadcrumb |
| Version: | 6.x-1.0 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
What Happens
When you drag and drop taxonomy terms on the List Terms page, the Taxonomoy module ends up calling the taxonomy_breadcrumb_taxonomy function in taxonomy_breadcrumb.module for a number of terms. I imagine the list of updated terms is determined via AJAX on the term listing page, but essentially the weights are adjusted accordingly to get the proper order.
Issue is, once you save the new order, the taxonomy_breadcrumb_taxonomy function is clearing out the taxonomy_breadcrumb_term entries for all reordered terms.
The line:
$new_path = $object['taxonomy_breadcrumb_path'];
is not properly setting $new_path for updated terms, so later, when the next line gets called (to check to see if the taxonomy_breadcrumb_term should be deleted), the delete happens for every updated term, when it should issue an update contained in the next elseif statement.
Why isn't $new_path being properly set for updated taxonomy terms?
I'm currently looking into this, but if anyone has any input in the meantime, please feel free to share.
Incidentally, this bug appears very similar to http://drupal.org/node/372813, but the solution proposed there seemed to fix that problem, so I created another issue.
I think the workaround is to manually set weights instead of dragging and dropping terms to reorder.

#1
Thanks for the info, I'm experiencing this bug as well.
#2
Can you verify that this problem happens in the current 6.x-1.x-dev?
There are two patches at #372813: Reordering taxonomy terms with drag-and-drop removes taxonomy breadcrumb path that need review. There was a problem with the initial solution that was committed, and these patches may fix it. So it would help if you could apply those patches (to 6.x-1.x-dev) and see if it works.
If the problem persists, please provide a step-by-step instructions to demonstrate the problem so it can be confirmed and fixed.
Thanks!
#3
I am closing this because the patches mentioned in #2 have been committed.