Closed (fixed)
Project:
Drupal core
Version:
6.x-dev
Component:
taxonomy.module
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 Nov 2007 at 21:22 UTC
Updated:
8 Dec 2007 at 16:08 UTC
Jump to comment: Most recent file
Comments
Comment #1
catchAlso it wasn't in the final patch, but somehow the relations select was nuked in the taxonomy ui cleanup, this one puts it back in. I don't mind rolling a one line patch for that, but it's the same chunk of code being affected so included with this for now.
Note that since we now show the parents and relations on taxonomy/term/add pages indiscriminately, including for freetagging vocabularies, this could be a big memory issue loading them. Oh and thanks to chx for irc advice on this.
Comment #2
chx commentedThanks for taking this issue. However, if you put the code inside
if (variable_get('menu_override_parent_selector', FALSE)) {then you need to negateif (!. Also, inside functions we only use // as the comments marker.Comment #3
catchthanks chx, this one should cover all that.
Comment #4
catchone comment wrapped at col 81
Comment #5
chx commentedUm, another ! left out.
Comment #6
gábor hojtsyOK, committed.
Comment #7
moshe weitzman commentedwhat does taxonomy_override_selector buy us that we could not already do with form_alter?
Comment #8
catchIn both of those forms the full taxonomy tree is loaded before form_alter can intercept. So as with the menu choosers, it allows you to insert drilldowns (or whatever) that can circumvent that.
Comment #9
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.