Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Had everything working according to plan with 5.x.2 without a problem.
Got tired of rewriting modules (rotor module and views headers and footers) to properly use wysiwyg API so tried an upgrade to 2x.dev version....now nothing is showing up at all.
Rebuilt my input formats...and re-enabled tinymce and button editor layout for "full-html" still nothing.
But everything works PERFECTLY in FF 3x.
I am using Tinymce 3.2.1.1 could that be the problem? Any input would be appreciated.
I am building out a D6x site from scratch for my end-users, but I need the 5x version to work for them until Super-Tuesday (election day)
I'm about to backport to the Tinymce module and import everything from another site where I've got it perfectly configured....but I hate to do it...I am more than willing to contribute and help resolve problems...but time is short.
I've attached a screenshot.
| Comment | File | Size | Author |
|---|---|---|---|
| wysiwyg-screwy.JPG | 42.81 KB | davedickens |
Comments
Comment #1
sun1) Please test whether you can replicate this issue in a Drupal core theme.
2) It may be possible that IE reached it's maximum of CSS files (~31) and tinymce's is simply not loaded (since I see the actual editor in your screenshot, but simply without styling, that may be a valid cause). Not sure how to test that, but enabling CSS aggregation might do the trick.
Please make sure you read the FAQ for Wysiwyg module (also linked from the project page).
If Wysiwyg API does not work as expected, please test whether it works
- after clearing/flushing Drupal's cache AND your browser's cache
- by temporarily switching to Drupal core's default Garland theme.
- after removing all wysiwyg profiles, create a new one, and in that profile, remove all plugins/buttons except bold + italic.
- by using the latest development snapshot.
- after disabling (all) other contrib modules (and if it does, re-enable them step-by-step to see who's guilty).
- in a different browser.
In case none of those steps make it work, then we need much more information in this issue. The editor and editor version in question, your browser and browser version, the web server software (Apache/IIS). Hence, setting proper status.
In any case, please report back about the status of this issue. Thanks.
Comment #2
davedickens commentedSUN....I just want to say something:
On behalf of all of us Drupalers out there....WE APPREACIATE YOUR EFFORTS!
I was completely and totally unaware that IE has a maximum CSS limit of 31.
As soon as I turned the CSS aggregator on....voila!
It would appear that that this was the issue.. (Either that or it just could not handle all the CSS needed)
I also used your implementations for coding http://drupal.org/node/531960 on the simplenews template and the latest 5x views module (which surprised me that it was not "up-to-code") to get them to work as well.
Thank you. I was pulling my hair out.
Can't wait to play with FAPI in D6.
You can close this one my friend.
-Dave Dickens
http://www.vbdc.org
Comment #3
sunWould you mind to add this bit to the FAQ? You might be able to avoid headaches for others by doing that. :)
Comment #4
davedickens commentedAdded to FAQ as requested.
Thanks.
Comment #5
iamwhoiam commentedOh my goodness, I had exactly this same problem on 6.x-2.x-dev
Stupid internet explorer. Thanks for the helps guys :)
Comment #7
aren cambre commentedTHANK YOU! Also fixed it for me.
Changing version so it's obvious it applies to the release for the current Drupal core, too.