Upgrade to Core 5.6 breaks Taxonomy Defaults
dabro - January 31, 2008 - 04:58
| Project: | Taxonomy Defaults |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | won't fix |
Jump to:
Description
I was happily using this module under Drupal core 5.3 to set a default taxonomy term to userprofiles and usernodes to hide these nodes using TAC. Under 5.3 it would set an active or not active term to these nodes. After upgrading to Drupal 5.6 it no longer will assign an active term to a node. It will still assign an inactive term to a node so I can still use it for what I want to do by using a term not active to the content type I want to assign it to. It's behavior seems to have changed with the core updates. Thanks for the handy module, Dave
#1
Dave,
Thank you for your kind words. There was a change to core taxonomy regarding the selection of terms when a category is required. I've tried to reproduce this issue, but was unable to. Can you please share your vocabulary and taxonomy defaults settings for the vocabulary in question?
#2
I'll try to explain my convoluted methods here. I'm using Taxonomy Access to control anonymous access to my users. I use default terms to assign terms to usernode and userprofile without the users having any input. I have a taxonomy vocabulary called viewing privilege. It contains one term called "private". This term is associated with the usernode content type. I use this to control anonymous user access using TAC. I also use "default term" module to set this term (which is inactive) for the userprofile content type to also control access to it. After upgrading core, the inactive term (private) still will be assigned to userprofile but the active term (private) will not be assigned to usernode. So it seems that the active term for a content type is no longer set by this module but the inactive term does still get assigned. I know something (at least it seems) in the core update changed the functionality. I hope this makes sense. Thanks, Dave
#3
I ran into the same problem: http://drupal.org/node/206064
#4
I'm unable to reproduce. What happens upon resaving the defaults?
#5
I've just upgraded from 5.2 to 5.7 and Taxonomy Defaults no longer works at all, I get a very long, gibberish-filled browser error message when I try to enter the category defaults screen in Safari. I get a blank page in Firefox. I deleted and re-installed the module and the same problem occurs.
Here's the Safari error: Safari can’t open the page “http://bigclosetr.us/topshelf/admin/content/taxonomy/taxonomy_defaults”. The error was: “Operation could not be completed. (kCFErrorDomainCFNetwork error 302.)” (kCFErrorDomainCFNetwork:302)
As I said, in Firefox, I got a blank page. Page source for the blank page was also blank.
- Joyce
#6
I've used this module many times before and it has always worked
But this time - I'm uisng the module Content Taxonomy (because of Hierarchical Select) and Drupal 5.14
is it one of these or both?
#7
@jwells,
This issue is only for sites that have been upgraded -- it sounds like you're building a new site. If this is correct, please file a new issue and try to give more detail. What isn't working?
There is another issue (#208467: Cannot have a default taxonomy term and a separate taxonomy CCK field?) regarding compatibility with CCK Taxonomy, which is different from Content Taxonomy, but you might read that issue and let me know if it sounds familiar.
#8
thanks - will do
#9
Calling this one "won't fix" unless (1) I see more demand from people trying to upgrade and (2) somebody gives some repro steps.
I think, at this point in the Drupal lifecycle, the window for fixing this has passed.