In the Category->Settings there is a field called "Content type settings", with a group of items called "Allow other content types to be:". I would like to be able to (optionally) allow only certain content types in a category/container. Especially when using autocomplete forms in CCK, I would like the categories to be created not to be of content type "category_cat" but of another category with more extended information.

Thus I don't have to prepopulate the categories before adding content of those specific types I require to have in that part of the hierarchy.

Comments

pkej’s picture

pkej commented
Title: Default "other content type" creation in categories/containers. » Re: Default "other content type" creation in categories/containers.

I wrote "Especially when using autocomplete forms in CCK," but it is with associated categories this problem occurs. Using a CCK field creates the right kind of datatype.

With this behaviour for associated categories I could remove the CCK fields in my content, and instead use the association for the data, thus creating all the right types of content everywhere on the site; automatically getting the benefits of the Category module.

And; I need a feature to transform a CCK taxonomy field to an associative link, so that I can convert my old data without writing the code myself ;)

JirkaRybka’s picture

JirkaRybka commented
Version: 5.x-1.x-dev » 6.x-2.0-rc1
Status: Active » Closed (duplicate)

This is a little unclear to my eyes, but I believe that it boils down to these points:

- Limit which content types may be inside a certain container. For tagged nodes, there's a setting of types that a container accepts (always was there). For categories, 6.x now have "allowed containers" setting on content types with category behavior, so I believe this part is fixed. (As for containers, these are actually top-level items, so there's no point in a setting like that.)

- Allow other content types with category behavior to be used for free-tagging or similar purposes. That's handled over at #251119: Allow various node types with category behavior to be used for free-tagging (per container).

- CCK fileds (taxonomy field). This is CCK business.

Also, 5.x branch is not really maintained now, and this issue was silent for over 2 years.

Closing now.