[note: although one can search for 4.6.0-rc issues, apparently one can't post them, which explains why I couldn't find any...]

Upgrading to the 4.6 release candidate made my primary site vocabulary disappear from the category settings. Because I use the same vocabulary for almost all site content, including forum topics, the upgrade process declared it a forum-only taxonomy.

1. The upgrade process should NOT touch existing vocabularies.

2. The ability to declare particular taxonomies as specific to a particular module (and defaulting to that state when the vocabulary is implicitly created through the administrative tools for that type) should be implemented in an upward-compatible way. It should not interfere with sites that use common vocabularies for their content.

3. All vocabularies, including module-specific ones, should be manageable from the category settings page (in addition to, for module-specific ones, the module settings page).

CommentFileSizeAuthor
#4 taxonomy.module_7.patch1.97 KBmikeryan
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

killes@www.drop.org’s picture

I agree that this needs fixing before the release. Changing the user's settings for taxonomies is a no-no.

walkah’s picture

Assigned: Unassigned » walkah

mine to fix.

mikeryan’s picture

Still broken - I did a clean upgrade with a more recent version of 4.6, it also broke my site vocabulary by stealing it for forum.module's exclusive use...

mikeryan’s picture

FileSize
1.97 KB

Here's a patch to enable management of all vocabularies in the categories page.

Hiding a vocabulary being used by forum.module may have some small benefit for those using that vocabulary only for forums, but it's a royal pain to the rest of us...

moshe weitzman’s picture

this was committed, i believe

mikeryan’s picture

Indeed, it's fixed in the current RC. Thanks!

Anonymous’s picture