Posted by ChrisZZ on April 24, 2009 at 12:55pm
Jump to:
| Project: | Content Taxonomy |
| Version: | 6.x-1.0-rc1 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Dear All,
content_taxonomy-6.x-1.0-beta6 and as well the latest beta the hinding function from beta1 is not working for me anymore. I had a look into the code, and i figured out, that the option also is not there anymore - even if there is a function for hiding those fields. Therefore i cannot hide those fields. Is that supposed to be as it is - is it a bug?
regards
Christian
Comments
#1
The behaviour has changed from beta5 to beta6. Form now on, only taxonomy fields, where a content taxonomy field with the same vocabulary exists, get hidden. if you want to hide any other taxonomy field, you have to change the vocabulary settings (associated content types)
#2
Well / if that is the standard behaviour, it does not work for me with the latest rc1. Am i supposed to disconnect taxonomies with content types for using that module?
#3
maybe same problem as here ? #463042: Taxonomy fields are not removed
#4
It might be the same problem . sounds like...
Can you point me to the mechanism, that should remove it?
#5
the removing of the fields happen in function content_taxonomy_form_alter (line 328). there, all vocabulary ids, where a content taxonomy field for this content type exists, get collected in $_content_taxonomy_vids. afterwards _content_taxonomy_taxonomy_unset($form['taxonomy'], $_content_taxonomy_vids) is used to remove the core taxonomy fields
#6
if (!is_array($form['taxonomy'])) {
return;
}
is true
how can that happen?
#7
Any recent developments with this issue? I switched back to taxonomy after i wasn't able to solve this, but now find i still need content taxonomy, so I'd like to know if there's a way to fix this. Cheers!
#8
Just found the culprit in my case. Since I realize its working for most people, I decided to check all modules I have connected to taxonomy and found that hierarchical select: taxonomy was conflicting with this module. Since I dont need it anymore, I won't investigate any further.
#9
well / i have hierarchical select installed / and need it...
#10
Any progress? I was using Hierarchical Select, but it has caused me more problems with other modules than I can count. I've given up on it temporarily, but would love to put it back at some point if there is an answer to this.
#11
I too will be abandoning Hierarchical Select in favor of Content Taxonomy. Can't have both the normal taxonomy inputs and the content ones showing in the node add form.
#12
Reopen issue if problem still exists.