In IE7 The error "JQuery Must be Loaded First" is thrown when Javascript compression is enabled in Drupal's performance options. Disabling WYSIWYG Image Upload seems to prevent the error from being thrown.

Comments

eugenmayer’s picture

eugenmayer commented

Well that one is already know - no idea how to fix this though. could be a jquery_update bug or anything in between. Anybody has a slightly idea?

newmediaist’s picture

newmediaist commented

It smells like a "weighting" issue - i.e. the WYSIWYG JS file is being loaded too early in IE7 when JS compression is on. As far as I know, it is not possible to set "weights" of JS files in Drupal 6 though?

eugenmayer’s picture

eugenmayer commented

Well how could a browser influence what the backend aggregates? Thats impossible.

newmediaist’s picture

newmediaist commented

What I am suggesting is it seems that IE is reading the aggregating file in a different method than Chrome/Firefox - which leads me to believe maybe chrome fire fox reads the whole aggregated file before trying to interpret the javascript, while IE interprets it chronologically as it loads

hence maybe the WYSIWYG Image Upload script is "too early" in the file for IE

Just a shot in the dark!

eugenmayer’s picture

eugenmayer commented

Hmm, well they all read it serialy. I think your thoughts are not in the wrong direction. What i suggest is that the IE is pretty sensible what is about the JS syntax. And i could think that some strange newline or braces are braking it.

how i hat those bugs...

newmediaist’s picture

newmediaist commented
Status: Active » Fixed

Upgrading to the newest DEV release of WYSIWYG seems to correct this issue by preventing the editor's JS file from being aggregated - seems to work fine in IE now w/ JS compression turned on.

eugenmayer’s picture

eugenmayer commented

Ok so this seems to be an issue with WYSIWYG? Thank you very much, i will add this to the incompatibilities section!

newmediaist’s picture

newmediaist commented

Correct - I believe upgrading to the newest DEV of WYSIWYG corrected this issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.