Made a demo of all currently supported editors, can be found here http://demo.foxinbox.org/node/add/test-content and found two issues. (Very clean and fresh install of drupal.)
Openwyswyg kills (other editors stop working, I believe it's jquery being killed).
Firebug doesn't give any openwysyg errors, but jquery errors out with saying $ is not a function (other jquery based items break. like admin menu, with similar errors). The http://drupal.org/project/openwysiwyg mentions that openWysiwyg conflicted with jquery, so not sure if that is related (as I believe it's worked before).
Unrelated but jqyswyg is throwing up an error "$(element).closest is not a function", but it doesn't seem to be breaking anything, at I believe closest is in a later version of jquery.
Comment | File | Size | Author |
---|---|---|---|
#16 | wysiwyg-DRUPAL-6--2.openwysiwyg.16.patch | 3.09 KB | sun |
#15 | wysiwyg-DRUPAL-6--2.openwysiwyg.15.patch | 2.91 KB | TwoD |
#13 | wysiwyg-DRUPAL-6--3.openwysiwyg.13.patch | 600 bytes | sun |
#5 | wysiwyg-HEAD.openwysiwyg.5.patch | 608 bytes | sun |
Comments
Comment #1
sunWow, thank you! :)
Comment #2
scottsawyerI'm getting this error from FF Error Console:
Using
IE Unlimited CSS Loader
Might that be the problem??
Comment #3
scottsawyernever mind, uninstalled openwysiwyg and installed FCK. problem solved, 20 minutes.
Comment #4
nquocbao CreditAttribution: nquocbao commentedIt's openWYSIWYG problem, they define their own '$' function ...
I replace $( with $openWysiwyg( in scripts/wysiwyg.js and everything works
Comment #5
sunCan we try this for openWYSIWYG?
Comment #6
nquocbao CreditAttribution: nquocbao commentedThe latest version can not detect openWysiwyg:
Library patch is defined as:
while we use
The change log file stays in editor folder, not the scripts folder :(
Comment #7
nquocbao CreditAttribution: nquocbao commentedAnd the patch does not work too.
Comment #8
sun#6 is caused by #752516-10: Version callback failed to open stream
Comment #9
nquocbao CreditAttribution: nquocbao commentedComment #10
sunSo let's try again? Not sure what
that has been mentioned in #4 is...Comment #11
EugenMayer CreditAttribution: EugenMayer commentedWell its about $ being bind to something else then jquery. But well, you cann use the normal enclosure trick here, which is used to also let jquery plugins work
Well in the other case, instead of replacing $ with $openWysiwyg, simply to the same arround the whole editor js implementation.
Comment #12
sunComment #13
sunSince D6 does not globally use jQuery.noConflict(); I fear there's little chance to solve this properly prior to D7.
Thus, attached patch reverts the addition of the $ closure in openwysiwyg.js, which worked previously and still works now.
Comment #14
sunThanks for reporting, reviewing, and testing! Committed to all branches.
A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.
That said, I'd welcome feedback on #970892: Drop openWYSIWYG support
Comment #15
TwoDAwww, and I was just going to throw another patch in here.
We don't need
jQuery.noConflic()
. It just reverts$
to what it was before jQuery was loaded, which in our case is undefined since we load openWYSIWYG after jQuery.Instead of manually overriding methods on the global WYSIWYG object to swap between the versions of $, why not automate it?
$ = old$;
instead of$ = jQuery;
makes this temporary replacement survive nested calls to methods without needing a "depth counter" to know when it's safe to revert to jQuery's $.Comment #16
sunCrazy TwoD, just crazy :)
Comment #17
TwoDXD
Comment #18
sunThanks for reporting, reviewing, and testing! Committed to all branches.
A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.