Does NOT remove default taxonomy fields from content types

The attached file brings content_taxonomy.module up to speed with Drupal 6 compatability as far as Coder is concerned and also adds in content_taxonomy_form_alter() for Drupal 6 to remove taxonomy fields from content types using the content_taxonomy CCK field.

For completeness here's the patched content_taxonomy.module

in Drupal 6 it's not required to select any content type for a vocabulary. If someone doesn't want that the core taxonomy fields shows up, he can simply unselect the content type in the vocabulary settings. or does this have any disadvantage?

I wonder whether the function ought to be included, though, since if a user does select the content type for the vocabulary then the vocabulary ought to be removed from the node edit form.

I added a checkbox to the field settings with 'Hide default taxonomy fields on the node form' (in advanced settings). If at least one content taxonomy field per content type is set to this option, the default fields from the core taxonomy module get hidden. So, hiding of the default taxonomy fields is optional now :)

Hey, nice one. Sounds good.

I'm using content taxonomy together with CCK and taxonomy. If I set the option 'Hide default taxonomy fields on the node form' it still keeps on showing the default taxonomy fields in the node form!

How is this possible?

For now I unchecked the content-type in the taxonmy vocabularies and for my required functionality that's fine but I would like it to work "proper" for future extra fuctionalities.

just set this post to active again

Hi!

In which folder is the content_taxonomy module installed?
under modules/content_taxonomy or sites/all/modules/content_taxonomy?

should be under sites/.., otherwise it doesn't work because of the hook invocation order

Had this issue as well in beta4 and was able to resolve it by following mh86's advice (thanks!), and moving the content_taxonomy (and other user contributed modules) to the sites/all/modules folder.

I'm not sure if that warrants closing the issue, but for anyone else looking for a quick fix...

Allright... I Will definetly do that then.

But why is there a difference?

Well I followed your advice, but choosing to hide the vocabulary field now eliminates all vocabulary fields!

In my opinion, the correct workflow of this module should be as below. I certainly have a use case where I have many vocabularies (for user profile nodes) of which I just want to override one widget using content_taxonomy

- Vocabulary X is enabled for content type A.
- Admin installs content_taxonomy and adds widget to A.
- c_t hooks into the node form and add the c_t widget, and takes away the taxonomy *for that vocab only*
- A now displays c_t widget for vocab X, and not the actual taxonomy.module widget
- Any remaining vocabs are displayed as per normal in the generic taxonomy widgets

This seems like the common sense approach, and should not be that hard I don't think?

I close this issue because comment #15 is related to http://drupal.org/node/319724

I concur.

I've just posted a kind of solution and now it's possible to choose whether you want to display default taxonomy fields or not, http://vito.ho.ua/en/content/content-taxonomy-show-default-taxonomy-fiel...

oops, I see, sorry, I should be posting it there http://drupal.org/node/319724

Hi, sorry to re-open this ticket but I just enabled this module for using it instead of the normal taxonomy selection.
I use a single vocabulary for the "evento" content type, but this module doesn't override the default selection. I still see both of them and no way I can disable the default.

Am I doing something wrong?

there is no option to disable default taxonomy fields. What about the option another person mentioned above, to not connect the vocabulary to any content type at all but rather just add a content taxonomy field to the content type. Is that OK to do or not recommended?

one mistake (which happens from time to time) is, that people place contributed modules into the core module folder (drupal-root/module) instead of putting them into drupal-root/sites/all/modules
if content_taxonomy is located in the same folder as core taxonomy, it's not going to work.
hope this information helps

See also: #722994: Vocabularies section visible on node add/edit form when using hierarchical select widget
#443892: Hiding Taxonomy Term Forms when using content taxonomy fields not working anymore??
#700990: Does not hide core Taxonomy widgets

Not sure what to mark as duplicates of what, since there seem to be several separate causes for the same problem over the past couple years. Some of these issues seem to be exclusively tied to the hierarchical select module, and in those cases the problem does not occur with other widgets.

Reopen issue if problem still exists.