Does not hide core Taxonomy widgets

I am experiencing this issue. Core Taxonomy field is still visible after setting up Content Taxonomy fields. Module is installed in the correct location too (sites/all/modules). Is there a setting I need to turn on?

#6 should not be necessary; in my experience, with the current release of the module, the vocabulary is always properly hidden when it is controlled by a Content Taxonomy field.

Are you using rc2 or the dev version? Also, are you using the hierarchical select widget by any chance? See: #722994: Vocabularies section visible on node add/edit form when using hierarchical select widget.

See also:
#443892: Hiding Taxonomy Term Forms when using content taxonomy fields not working anymore??
#267622: Does NOT remove default taxonomy fields from content types

Reopen issue if problem still exists.

Having the same problem with 1.0-rc2. (after update)

No matter what I do, Vocabularies are still showing up.

All contrib modules are in sites/ of course. There is no conflicting modules such as hierarchical select.

Any ideas?

EDIT: Have also tried latest dev version and the same issue is happening.

#10: The core taxonomy fields are properly hidden for me. Maybe you could try to provide some steps to reproduce?

Getting the same thing here, whether or not I've set the widget to hide the existing input fields.

We're using Tabs to break up a rather lengthy form. When the form is tabbed, we get the double input fields -- one with an "add" button and one without. When we turn off the Tabs style for any given group, we get the correct display. So it appears, at least in our case, to be an issue with the Tabs setting.

We also get correct display when we use "collapsible" or "collapsed" styles. It's just the Tab style that is creating this issue.

Great module in every other way! We're excited about using this.

I get the same problem. Installed: Content Taxonomy. Activated a Content Taxonomy Field for a content type. Chose autocomplete widget (only one available in the list). Result: double taxonomy/vocabularies fields (core + Content Taxonomy widget). See screenshot. In effect it makes the Content Taxonomy unusable (for us, anyway), which is truly a shame since it seems to be a great module.

EDIT: BTW when I use the Hierarchical Select widget instead of, say, the autocomplete widget that comes with Content Taxonomy, everything works smoothly (read: the taxonomy field "double up" disappears from the node forms in question).

Subscribe +1

Same as. I'm using content profile, and the extra vocabulary form appears on the profile edit page. I can hide it using content profile's "Other form elements (except for required CCK fields)" but unfortunately that option also removes some hidden fields that cck private fields needs, so it's not an option.

subscribe

Well I don't see much happening here. That said I'd really like to find the cause of this problem. In my case selecting a different widget (See thomas1977 "EDIT: BTW when I use the Hierarchical Select widget instead of, say, the autocomplete widget that comes with Content Taxonomy, everything works smoothly") has no effect whatsoever.

Perhaps we could move it forward by pinning down where this damn extra field is being generated from (any suggestions how we might do that? Looking at firebug doesn't give much of a clue in my case: a fieldset with a label of "collapse-processed").

Or maybe examining the installed modules in common. I'm presuming most (all?) of us have content-profile, content taxonomy and hierarchical select installed. I'm also using private fields. What about the rest of yous?

Anybody got any ideas? Anybody have all or some (which?) of the above modules installed?
Which version of cck are yez using? I'm on 3.

Same problem here. It's kind of major bug and I can't believe that there's still no fix for such a long time!

BTW, I don't use Content Profile or Hierarchical select, or anything like this.

#12 @pbeakley - "set the widget to hide the existing input fields" - is there such setting?

Ok, fixed it by changing module weight to 1 (Core taxonomy weight is 0).

Re: #19 -- To clarify, making the module's weight (core + 1) resolves the main issue?

If so, we should patch hook_install() along with a hook_update_N() to set the module's weight.

Yeah, #19 fixes the issue, content taxonomy should be executed after core taxonomy.

I changed module weight and I still get a double display on the node. The Content Taxonomy filed and the core taxonomy filed are both being displayed. I do not get two forms on edit though.