This was a tough issue to track down and I'm not quite sure why it is happening. So I'll document my test results to hopefully show when the issue arises.
Basically the combination of the acquia marina theme, the admin menu and using the WYSIWYG (module) + TinyMCE (library) in IE7 causes the TinyMCE editor to break on any add/edit page. See attached screenshot.
Here is what I've tested so far...
Acquia Marina + Admin Menu + WYSIWYG/TinyMCE + IE7 = Fail
Acquia Marina + Admin Menu + WYSIWYG/TinyMCE + FF = Pass
Acquia Marina + Admin Menu + WYSIWYG/TinyMCE + Chrome = PassGarland + Admin Menu + WYSIWYG/TinyMCE + Any browser = Pass
Acquia Marina + WYSIWYG/TinyMCE + Any browser = Pass
Let me know what I can do to help track this down.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | acquia_marina_comments_issue.png | 15.47 KB | caschbre |
| acquia_marina_admin_menu-ie7_issue.png | 5.47 KB | caschbre |
Comments
Comment #1
caschbre commentedOk, after a little more investigation this may not be tied to the admin menu. I removed access to the admin menu and that corrected my node add/edit pages, however I'm still seeing this issue on comments. I have the comments entry enabled to display below the node and I'm seeing the same issue (see attached screenshot).
Comment #2
caschbre commentedI've changed the title of this issue after further investigation. I'm now thinking that maybe some theme settings are corrupted. So I'm also changing this to a support request and not a bug.
Here is a little more background on what I'm doing.
I created a sub-theme using acquia marina as my base theme. I copied the theme-settings.php, acquia_marina.info, and style.css files to my sub-theme. I renamed files and edited files changing the names of functions, etc. I've done this on two sites and both were working perfectly up until this weekend. One is still working perfectly.
I've been trying all sorts of things to correct this issue. When I went to my sub-theme configuration I hit the "reset to defaults" button. This corrected the TinyMCE on IE7 issue. The theme settings on the configuration screen are back to their default values however the site isn't using those values. The site is still using the values I had prior to this weekend. If I hit save settings on the sub-theme configuration, even without making changes, then the issue pops up again.
So I thought maybe my sub-theme was corrupted. I copied my sub-theme css into the acquia marina local.css file and switched back to that theme. The TinyMCE and IE7 issue is back. Clicking reset theme defaults does not correct the issue.
So at this point the only thing I can think of is that somewhere along the way the theme settings became corrupted in the database. Since I don't see a way to uninstall a theme I'm sort of at a loss at how to proceed.
Comment #3
caschbre commentedAfter some more investigation...
Admin menu still has to be disabled when using tinymce/wysiwyg. See above posts. I also had to disable the quote module.
And I even had to stop using the "upcoming" view block that is created with the calendar module. Though I created a new view and made a duplicate of just that view block and that works. I'm guessing maybe because it doesn't include some of the calendar.js files / script code when generating the page.
I even tried to build the site from scratch again and came across the same issues. The additional html output when using those modules causes wysiwyg+tinymce to break down on the acquia theme. I'm not having the issue on other themes.
Comment #4
tutumlum commentedsubscribe..
Comment #5
medwassim commentedI thik that the CSS file for tinymce editor have not been loaded.
try to add this on your custum module :
drupal_add_css(drupal_get_path('module', 'tinymce') .'/tinymce/jscripts/tiny_mce/themes/advanced/skins/default/ui.css');
Best Regards
Comment #6
caschbre commentedI'm not sure I understand where to add this.
Comment #7
Monzer Emam commentedAlmost I have same issue.
And the root cause was that the IE has a limitation of max 30 css file per page.
So to solve this visit "Administer » Site configuration » Performance" then set "Optimize CSS files:" to Enabled.
Comment #8
druplicate commentedIE SUCKS!
Had the same problem when I enabled the location and gmap modules and that added two more CSS files which caused grid16-960.css from Fusion core to be bumped off the list which really broke the layout.
Turning on CSS optimization packs 'em all into one condensed file, obviating the problem.
What a pain!
I always turn off caching and css optimization when doing theme development so I don't have to clear the cache every time I make a change to some CSS file and this is the first time this has been a problem.
Thanks for the tip!
Comment #9
jeremycaldwell commentedHi drupilcate, when developing you can turn on the "Avoid IE Stylesheet limit" option on the theme's configuration page rather than enabling CSS compression and having to clear the cache each time you make a chance. This is in all Fusion based sub themes so it won't work for Acquia Marina 2.x, but the 3.x will.
It doesn't compress the CSS files but does an @import to load them for IE. It's a bit slower than using CSS compression of course but it's a great alternative when developing. When you are done developing your site you can re-enable CSS compression and turn off the "Avoid IE Stylesheet limit" option and you would be all set. Hope that helps!
Comment #10
Monzer Emam commentedHi eternalistic,
Thanks for input, Both work around should be documented in some where in drupal handbooks itself I guess.
Comment #11
jeremycaldwell commentedAt the moment the majority of documentation regarding Fusion is on the www.fusiondrupalthemes.com website. The one about the IE stylesheet limit is located here: http://fusiondrupalthemes.com/support/documentation/troubleshooting/my-s...
Comment #12
Monzer Emam commentedAlso http://drupal.org/project/unlimited_css solve that issue (didn't try it yet).
Comment #13
henkit commentedHi Monzer,
Optimize css files worked for me!! Thanks :)
Henk
Comment #14
jeremycaldwell commentedMarking this as "by design" because this an IE issue with how it handles a certain amount of stylesheets (31+). This issue should be easy to find though so not marking it as closed.
Comment #15
renyi commentedThanks for both the tip.
I would like to add however, optimize CSS did broke my site once. Maybe due to css errors from modules or themes or maybe my private css overrides. (Sorry, I didn't have the time to check) I disabled it and everything back to normal.
It didn't really bother me that time, as I thought it was only doing CSS compression.
So use this option with care ! (and backup of course ..)
Also, I was not using Fusion then. I just thought enabling this will compress CSS and make the website somewhat faster.