I have no problem setting a default taxonomy term for a content type with this module. But, if the content type has another taxonomy field (from a different vocabulary than the default term's vocabulary), the default term no longer works and only the selected taxonomy term from the CCK taxonomy field shows up. Am I missing a crucial step somewhere or does this module not work with additional CCK taxonomy fields? Thanks in advance.

Comments

heine’s picture

heine commented
Category: support » feature

This module has not been designed to work with CCK taxonomy

hillaryneaf’s picture

hillaryneaf commented

Are there any work arounds? Has anyone in the past tried to achieve this?

hillaryneaf’s picture

hillaryneaf commented

This is my workaround:

I found a solution until the above module is updated with the feature...

Using the Form Markup Module, I created a taxonomy CCK field in my new content type, called something like "default news category" and set it's default term to news. I set it to required and in the Form Markup prefix field (supplied by the module) I put in the necessary html/css code

<div style="display:none;">

and in the suffix field

</div>

This way the field will not display to the user when they add content with this particular content type and it has a default taxonomy term or terms.

I hope this helps someone else out there!

hillaryneaf’s picture

hillaryneaf commented
Version: 5.x-1.x-dev » 5.x-1.0

Tried it in the official release but still does not work with cck taxonomy... so I updated the version on this feature request.

bradweikel’s picture

bradweikel commented
Version: 5.x-1.0 » 5.x-1.x-dev

I'm willing to look into addressing this issue (just adopted the module), but can't reproduce the problem. Can somebody give me a clear, simple test case?

bradweikel’s picture

bradweikel commented
Status: Active » Postponed (maintainer needs more info)
hillaryneaf’s picture

hillaryneaf commented
Status: Postponed (maintainer needs more info) » Active

Here's a test case:

- Create a vocabulary (for example "Year") and add some arbitrary terms
- Create another vocabulary (for example "News Type") and add some arbitrary terms
- Create a new content type
- Add a taxonomy CCK field from vocabulary 1 ("Year")
- Add another taxonomy CCK field from vocabulary 2 ("News Type")
- Set a taxonomy default for the content type - use Year and pick a term
- Now add a new content item with this content type, fill in the taxonomy News, but not Year

The taxonomy default for Year that was set, will no longer be set.

bradweikel’s picture

bradweikel commented
Status: Active » Closed (won't fix)

Given the new trajectory of Taxonomy Defaults in D6 and D7, and that the CCK_Taxonomy module was never upgraded to D6, I'm not going to put time into fixing this one in 5.x -- but if somebody else rolls a working patch I'll review and commit it.

bachbach’s picture

bachbach commented

Thanks for trick nektir !
Or you can just hide the "default" taxonomy content field with "content permissions" from cck module.