Taxonomy fields are not removed

is this problem new for you since rc1? or same problem with any other release?
sometimes people put contributed modules directly into the /modules folder (where core modules are located), instead of /sites/all/modules. if content taxonomy is located directly under /modules it won't work

Im working on a fresh install of D6, and the module is located under sites/all/modules. I installed the b6 version and then i upgraded it to the latest release and in both cases it doesn't work for me. I remember I once found a hack to do it in D5, but was excited i wouldn't have to do anything in this version since the module removes the taxonomy field by itself... i hope i can get it working the way its supposed to.

it would be very helpful, if you can provide following information
- vocabularies and configurations
- Content Taxonomy fields used and configurations (voc, widget type, 'Save values additionally to the core taxonomy system')
- content type used
- screenshot of the node edit form

OK. Here's what i got: I have two vocabularies, 'categories' and 'keywords'. They are both two-level vocabularies assigned to the same content types (User Blog, for example). Categories is required and single-choice, and Keywords are optional and multi-select. Both of these were set with hierarchical select (also tried removing it to see if issue went away, but no). My two content taxonomy fields are set to hierarchical select as well, with the same settings (required/optional), and set to their respective vocabularies. I also set the field name the same as the vocabulary name. I tried making EVERYTHING the same in order to get it to work. I can't provide a screenshot at the moment, but it just shows duplicate form elements (ex. below).

Category:
[dropdown]

Keywords:
[multiselect]

Content:
[textfield]

...

Category:
[dropdown]

Keywords:
[multiselect]

I mark this as duplicated because of #443892: Hiding Taxonomy Term Forms when using content taxonomy fields not working anymore??

I'm having the same problem and I'm confused. Why wouldn't we put the module into the /modules directory when the instructions clearly state:

Installation:
-------------
1. Install this files into the modules directory of your choice (for example, sites/yoursite.com/modules/content_taxonomy).
2. Enable content_taxonomy.module in the admin/modules page
3. Enable wanted widgets in admin/modules (e.g. content_taxonomy_select.module) Note: all require content_taxonomy.module!
4. Optional enable content_taxonomy_views.module for improved taxonomy-views support

What am I missing?

Edit: Sorry...I guess this is a contributed module that allows us to hide the core taxonomy? Where can I get this?