"Duplicate entry" error when same vocabulary & ccktssu field are enabled (token related)
| Project: | CCK Taxonomy Super Select Ultra |
| Version: | 5.x-1.1 |
| Component: | User interface |
| Category: | support request |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Because of -what I suppose to be- a bug of cck_taxonomy_ssu tokens, the parent issue, using pathauto and auto_nodetitle requires for me to use enabled vocabs on nodetypes where cck_taxonomy_ssu fields for this vocab are still used. I still use the cck_taxonomy_ssu.module because I intend to replace the terms by the cck_taxonomy_ssu fields, so much more practical, on a very big amout of node (meanwhile apparently tokens don't work and operations don't exist). I can partly hide my terms thanks to the term_display.module (or probably with some node.tpl theming later on).
This leads me to the "Duplicate entry" error :
user warning: Duplicate entry '551-112' for key 1 query: INSERT INTO term_node (nid, tid) VALUES (112, 551) in /Shared Items/iDoc/drupalpp/includes/database.mysql.inc on line 172.
and to display twice the terms to tag the node with, making thing confusing for my editors: once in the ccktssu fields and once under the category fieldset.
Suggestions:
- Could there be an option for vocabs to be enabled at the same time but not shown both on the node view and add/edit pages? Or
- just leave the error message while precising: "vocabulary-name" should not be enabled on the 'nodetype' where exists a ccktssu field for that vocabulary in this 'nodetype'.
Many thanks in advance. Arsène
#1
Another parent issue could be the #202995: adopt pre-existing tags into ccktssu feature request. Although the ccktssu.module is clearly described there as requiring the concerned vocabs to be disabled.
#2
If you have enabled the option in CCKTSSU to mimic the regular tag functionality, then of course you are getting this error since you are also using regular tags. Choose one or the other, but not both.
#3
If the terms and ccktssu values from the same vocabs had different purposes and the fields did not require the tag functionnality, (which is another case of mine, reported under the labels issue), then leaving unchecked the ccktssu fields solves the problem.
This is not quite my problem here. I don't intend to mimic the tag functionality, just to keep some token features in order to get my nodes correctly titled. But I don't like the weighting of the terms which is for-all-nodetype by defaults, and the term_display per-nodetype which yet can't cope with the much more flexible CCK display system, which ccktssu does so well!. And this why I keep the ccktssu field feature in my node! I intend to use ccktssu instead of the vocabs in this particular case.
And I need all my nodes, increasing by tens of dozens each day, to be ready for the ccktssu-unique-use migration, that is to say for each node to already have their ccktssu field *and* related terms tables up-to-date when disabling the vocabs. This will be possible when tokens will work (reason for marking the topic as "minor")!
#4
Well, just to make sure that you understand: enabling the tag feature of ccktssu writes data to the same place as a regular taxonomy and so you'll get collisions there. You can't enable a vocabulary for a content type where you already have ccktssu in use.
#5
Automatically closed -- issue fixed for two weeks with no activity.