[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).
Comment | File | Size | Author |
---|---|---|---|
#4 | taxonomy.module_7.patch | 1.97 KB | mikeryan |
Comments
Comment #1
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedI agree that this needs fixing before the release. Changing the user's settings for taxonomies is a no-no.
Comment #2
walkah CreditAttribution: walkah commentedmine to fix.
Comment #3
mikeryanStill 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...
Comment #4
mikeryanHere'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...
Comment #5
moshe weitzman CreditAttribution: moshe weitzman commentedthis was committed, i believe
Comment #6
mikeryanIndeed, it's fixed in the current RC. Thanks!
Comment #7
(not verified) CreditAttribution: commented