Closed (won't fix)
Project:
Content Taxonomy
Version:
5.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
4 Oct 2007 at 21:54 UTC
Updated:
1 Sep 2010 at 10:19 UTC
It appears that the taxonomy field has a conflict with the taxonomy_defaults module. taxonomy_defaults automatically associates a default taxonomy with a node whenever a new node is created. It works fine, except when the content type contains a taxonomy field.
The way that taxonomy_defaults appears to work is that it overrides the nodeapi method and simply sets a default taxonomy in the $node->taxonomy. I am guessing that this is done before content taxonomy is called, which wipes out the previously set taxonomy.
I'd imagine this is a quick fix? Let me know what you find.
Comments
Comment #1
ilmaestro commentedOk, the issue is occuring in content_taxonomy.module in the content_taxonomy_field method:
So what is the purpose of that bit of code? Why are we unsetting all previous taxonomy for the node?
Comment #2
alexh commentedHi,
I had the same problem and it seems to be solved like that:
Remove or comment out the unset in the function content_taxonomy_field in content_taxonomy.module:
...and change the function taxonomy_defaults_nodeapi in taxonomy_defaults.module:
Comment #3
dynv commentedI'm having this issue as well. It would be nice to have something committed so I would be able to combine both module as I would prefer.
Comment #4
internal commentedSubscribing...
Comment #5
momper commentedsubscribe
Comment #6
ttaylor797 commentedI had the same issue with taxonomy terms not taking to the db post submit, and only had to change the content_taxonomy.module line 126 as per #2.
Thanks Alexh!
Comment #7
hapydoyzer commentedsubscribing
Comment #8
magnus commentedCleanup of old issues. According to maintainer: "active development is only done for the 6.x branch! 5.x is not supported any more".
Open a new issue if problem still exist.