Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I have a custom theme I am currently developing. All was fine till 1.9, but after tonight's update to 1.10 a weird thing happens that is truly beyond me...
This only happens in IE8 under windows (I check only that version and latest firefox 3.5.x, 3.6.x and 3.7.x, so I could be other browsers as well). I reverted back to 1.9 and it doesn't happen there. So I upgraded to 1.10 again to troubleshoot this a bit more. I noticed that when I remove (actually rename) the block_edit.css file the issue goes away. I tied removing all styles from the file and that's where the weird part of this issue starts... it even happens with an empty block_edit.css file!
Any ideas any one?
Comments
Comment #1
klonosCould this be related to implementation of node edit links? #508658: Does a node edit corollary exist?
Comment #2
klonosAfter some more troubleshooting I hit F12 in IE and saw that the first css file loading is gallery_assist.css from the Gallery Assist module. I use the latest stable release 1.9-rc2 dating 03.02.2010.
I initially disabled the module altogether (renamed its folder) to quick-test if something was wrong with it and it proved that my thoughts were correct. I then disabled (renamed) only the gallery_assist.css file and re-enabled the Gallery Assist module (reverted back to its original folder name). This made the issue go away. So perhaps a conflict between the two modules after Block Edit 1.10 or what?
I tested with Garland theme and it doesn't happen, but then again that is a simple theme with not much css and all. So I am guessing that others might be having this issue in their custom themes when both modules are installed and enabled (?).
Any thoughts as to how to troubleshoot this further?