Hi
When i select a vocabulary for content taxonomy, it is no longer visible under vocabularies in node edit form. I know it was working before but even when reverting to beta 6 it still does not work.
Is it the update to drupal 6.12 that is causing the problem?
I need this because i use a free vocabulary to enter terms, I save the page and then i can use content taxonomy with select boxes for the same vocabulary to choose which terms i want to show, make collapsed or hide.
My solution for now is to disable content taxonomy, add term to the page, enable content taxonomy and then select which terms i want to list.
Any easier solution?
Thanks
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | content_taxonomy_patch.diff | 3.41 KB | oknate |
Comments
Comment #1
Bilalx commentedFound the culprit. It was _content_taxonomy_taxonomy_unset() function in content_taxonomy.module
Added a return in the first line but it would be nice if the "unsetting" was not automatic
Comment #2
edegro commentedI had the same issue, I commented this out in content_taxonomy_field():
And commented the entire content_taxonomy_form_alter() function.
The TagTool stopped working when I installed Content Taxonomy. Its vocab specific settings kept getting wiped out. So far, since I made the above changes to Content Taxonomy, it hasn't been a problem again. Not going to say for sure, but I think there is a conflict there.
Comment #3
mh86 commentedsince some versions of content taxonomy, core taxonomy vocabulary fields get hidden as soon as a content taxonomy field with the same vocabulary id and content type exists. otherwise we might get some conflicts or we would need a different logic to remove core taxonomy fields.
it's difficult to make the behaviour suitable for every use case ;-)
Comment #4
tuffnatty commentedThe correct logic is already described in the comment for content_taxonomy_form_alter():
but the field option 'hide default taxonomy fields' is not implemented yet. Patches are welcome?
Comment #5
oknatesee comment below. Comment deleted.
Comment #6
oknateI created a patch, based on the comments above. Seems to work fine. Allows you to have field without it removing vocabulary from taxonomy section of node form. It adds a checkbox to the field settings for this option.