conflicts with content taxonomy module
| Project: | Term Merge |
| Version: | 5.x-1.1 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Hi, thanks for contributing this handy module!!
Unfortunately on my site it badly messed things up for me, because I am using the content_taxonomy module. This module provides CCK fields which can present taxonomy terms but optionally allows to store the chosen term(s) in the content_type_x table.
Thus when this module replaces the old term IDs in the db with the new one, it needs to also do this in the content_type_x table as follows (for example):
UPDATE content_type_mytype SET field_ccktaxfieldname_value = 11 WHERE field_ccktaxfieldname_value = 5;
...where:
* mytype is the CCK node type
* field_ccktaxfieldname_value is automatically generated by CCK from the CCK taxonomy field name
* 11 is the new term ID
* 5 is the old term ID
Let me know if this doesn't make enough sense :)
