Closed (fixed)
Project:
Drupal core
Version:
4.7.x-dev
Component:
forms system
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 Dec 2006 at 10:57 UTC
Updated:
13 Jan 2007 at 19:00 UTC
Jump to comment: Most recent file
Comments
Comment #1
heine commentedNote: it doesn't just happen to the node submission form; try the following with and without theme_test_form().
Comment #2
heine commentedExperimental, so no 'needs review'. Patch takes the approach that prefixes cannot be touched by the elements theme function.
Comment #3
anders.fajerson commentedThis indeed makes the patch in http://drupal.org/node/100775 work. Can't really comment on the implementation, but I'm tempted to set this as critical.
Comment #4
anders.fajerson commentedSorry, missed the "no" in "so no 'needs review'.
Comment #5
heine commentedApart from having an inconsistent and broken implementation, consequences of this bug are:
Comment #6
heine commentedComment #7
chx commentedComment #8
heine commented#7 is much more elegant. This patch (or similar) needs to go into Drupal 5 because our javascript may break when divs are moving around when someone creates a theme_form_id override (upload, collapse).
#7 fixes the issue and did not introduce other problems during testing.
Comment #9
dries commentedIt's hard to understand/grok that change. What exactly is going on? Inheritance? And can we document that in the code?
Comment #10
dries commentedCommitted to CVS HEAD.
I think this needs to be backported so changing the version. :)
Comment #11
killes@www.drop.org commentedchx will re-roll later
Comment #12
chx commentedIndeed he will.
Comment #13
killes@www.drop.org commentedapplied
Comment #14
dwwFYI: the only "downside" of this patch is that modules which used to use #prefix to add a div to their node form used to see the divs in this order: .node-form .custom. now, it's reversed: .custom .node-form. this has been screwing up the CSS for the project_release [1] and project_issue [2] UI. not the end of the world, but just thought i'd mention it. ;) i already documented this at http://drupal.org/node/64279#prefix when i ran into it during the 5.x port of project*, but it appears this is now an issue for 4.7.4 -> 4.7.5 porting, too. should we add such a page? anything else change between 4.7.4 and 4.7.5 that needs documentation like this?
thanks,
-derek
[1] http://drupal.org/node/105228
[2] http://drupal.org/node/105229
Comment #15
dwwhttp://drupal.org/node/105960 is now there.
setting everything back for posterity.
Comment #16
(not verified) commented