Major incompatibility issue (mootools causing havoc)
-
-
- GWS-Desk
- Sr. Rocketeer
- Posts: 132
- Thanks: 0
-
Billy Zoellers wrote:
well if it works on a bunch of peoples computers, maybe it is not issue with the template or bot at all. maybe it is your server.Protective mode are we?
who says it works on others computers? so far only AM has reacted with defund reaction. As stated..... client (not on our server has reported the issue), we have installed the template on
jmd2.info
which is a Rochen hosted server and one of our testservers...Here we have the issue.......... (plain Joomla nothing else for JCE and (!) FCK) We have installed on
jmd12.info
which is also a Rochen hosted system and here we have the same...... Next client is hosed at Hostgator and has same issue.... so don't go into protective mode but think solutions....this is no attack on RT.... it needs a solution and avoiding the issue like the plague which is being done now by the producers does not help
thanks
Leo - For Professional Web-Development::
http://gws-studio.com
For Specialized Joomla Support:: http://gws-desk.com
For Specialized J-hosting:: http://gws-host.com
-
-
-
- GollumX
- Elite Rocketeer
- Posts: 2817
- Thanks: 0
- Sounds like a legitimate issue. IMHO though JCE should drop jquery and get on the mootools boat. I'll request this via their contact form and suggest everyone else do the same.
- Say no to Internet Explorer 6.
twitter.com/mark_up
-
-
-
- James Spencer
- Preeminent Rocketeer
- Posts: 46340
- Thanks: 50
- A direct link for the request form for us lazy Rocketeers would be awesome ;D
- James Spencer / Developer & Support / Hull, UK
-
-
-
- Daniel Chapman
- Elite Rocketeer
- Posts: 1258
- Thanks: 0
-
Can you please answer these:
Why not remove mootools yourself?
Why not use wysiwyg pro? Why must it be JCE?
Why not try removing slimbox?
You are doing your fair share of protective mode also so please keep the personal attacks to a minimum. You are demanding a solution but refusing to accept anything that isn't exactly what you want - a change to RT templates to make them work with JCE on the front end.
Unfortunately RT doesn't control Mootools.
Have you done enough testing to determine that it is in fact mootools or something specific about the mootools implementation?
E.G. get a non mootools template, just include the mootools js in the index.php and then install JCE and test it without the extra scripts suck as roktools or slimbox.
If it is a -mootools- problem, then the only solution RT can provide is to remove mootools from the templates.
Removing mootools would mean 1 of two things:
1. the templates lose their excellent functionality and RT would steadily lose customers to other clubs who were still using mootools - ie almost every other club - effectively suicide for RT.
Btw I was surfing the clubs tonight and the latest templates from almost every single one of them use mootools in some way. So if it is mootools causing the problems - good luck getting them all to remove mootools so your users can use JCE!
2. They replace mootools with another js library, and RT templates will in all likely hood no longer be compatible with Joomla 1.5 - also effectively suicide for RT.
So please check if the problem is mootools or how RT uses mootools. Then come back and let us know. -
www.ninjoomla.com
- The Ninjoomla Open Source Extension Club
Over 50 open source extensions and 100 videos to you build the site you want.
-
-
-
- GWS-Desk
- Sr. Rocketeer
- Posts: 132
- Thanks: 0
- www.cellardoor.za.net/index.php?option=com_contact&Itemid=34
- For Professional Web-Development::
http://gws-studio.com
For Specialized Joomla Support:: http://gws-desk.com
For Specialized J-hosting:: http://gws-host.com
-
-
-
- Daniel Chapman
- Elite Rocketeer
- Posts: 1258
- Thanks: 0
-
I just checked the latest JCE and it uses mootools!
This might be your problem right there. Including the libraries twice.
For this exact reason all my mootools modules have a parameter 'include mootools script'
Ok try this out. Go to the mootools website.
Download a full mootools script, or if you have time, check what modules you need for RT and JCE and only include those. I recommend taking all though just to be sure.
Then replace the mootools file in the template/js directory with the newly downloaded one.
Now install JCE, then ftp/joomlaxplorer your way to the install directories.
go here -> jscripts/tiny_mce/libraries/jscripts
then rename the mootools.js to something like mootoolsold.js so that it no longer gets included.
Then try it. Jce should now be using the new mootools file, the same as RT should be.
possible problems:
there is a file in that directory called mootools_basic.js I am not sure of the purpose of this file. If the above doesn't work, then rename this file too.
Also I didn't check every folder in the JCE installation, they might have another mootools file included somewhere. (I doubt it though) -
www.ninjoomla.com
- The Ninjoomla Open Source Extension Club
Over 50 open source extensions and 100 videos to you build the site you want.
-
-
-
- GWS-Desk
- Sr. Rocketeer
- Posts: 132
- Thanks: 0
-
Daniel Chapman wrote:
Can you please answer these:you pas the issue at hand.. I am not blaming nobody, i am pointing tio the issue that it is mootools related. I have not stated that i dont like RT nor have I stated that I dislike JCE or FCK ..... so dont bring this to a personal level nor to attacking mode... I did not dop that and i would love the systems to work together! Why are you so aggressive? I post an issue we experiencing and pontb to most likely cause (actually Ryan Demmer of JCE posted this as cause on his forum) So whats wrong with posting an issue an looking for a solution ? Why you feel attacked and react accordingly? I miss out on that and i dont even want to discuss that. I posted an issue and try to find a solution....
Why not remove mootools yourself?removing or changing is not a solution. I am not used to run away for issues and try to resolve them......Why not use wysiwyg pro? Why must it be JCE?Mosts clients love JCE and dont like WYSIWYG....not a matter of commercial...I need to go to WYSIWYG to be able to run RT-templates? Is that an advantage for the user? weird......Why not try removing slimbox?I dont want to remove anythingg...i just want it to work together... Your solutions are diving with your head in the sand which are no solutions but avoiding problems and hiding for them.... I have not seen a single solution besides avoiding the issue... THAT is not how WE operate!
You are doing your fair share of protective mode also so please keep the personal attacks to a minimum. You are demanding a solution but refusing to accept anything that isn't exactly what you want - a change to RT templates to make them work with JCE on the front end.I am not aware that i am attacking at all. I have not been attacking at all... i have posted an incompatibility issue and if you cannot live with that fact you have a problem/////
Unfortunately RT doesn't control Mootools.never said they did...... I mentioned that RT posted in several relases of templates improved mootools...anything wrong with that?Have you done enough testing to determine that it is in fact mootools or something specific about the mootools implementation?Yes and see posts regarding that on JCE-BoardE.G. get a non mootools template, just include the mootools js in the index.php and then install JCE and test it without the extra scripts suck as roktools or slimboxno need even Ryan said it was caused by mootools... Which does NOT conclude that RT is to blame.... Nobody said that! Again why bringing it to that level? Agression does not resolve this issue. Clinet has posted, we have tested and we have posted with the issue....whats wrong with that? Looking for a solution for a client?
If it is a -mootools- problem, then the only solution RT can provide is to remove mootools from the templates.Maybe, just maybe in the interest of clients who pay for services (and we do as well as our clients) the persons involved here could communicate: Cellardoor and RT are very well acquainted so where is this going wrong i would say? Again nobody to blame but a solution is thought after, again whats wroong with that? I am not interested to hack files, remove code for the sake of making it work....I think thats final and a terminal approach and not in interest of users especially end-users.Removing mootools would mean 1 of two things:Not requested..... maybe a handshake between RT and JCE/FCK would help..............
1. the templates lose their excellent functionality and RT would steadily lose customers to other clubs who were still using mootools - ie almost every other club - effectively suicide for RT.Btw I was surfing the clubs tonight and the latest templates from almost every single one of them use mootools in some way. So if it is mootools causing the problems - good luck getting them all to remove mootools so your users can use JCE!It is not against mootols or RT or JCE or FCK please refrain from pushing this in wrong direction since you will not succeed... It is not about my users...it is about paying RT/JCE-users sorry for the slight correction in your perception which is wrong
2. They replace mootools with another js library, and RT templates will in all likely hood no longer be compatible with Joomla 1.5 - also effectively suicide for RT.you bring irrelevant argments in the discussion despite being valid arguments
So please check if the problem is mootools or how RT uses mootools. Then come back and let us know.Again dont feel attacked..I posted a valid issue we are facing for client sake and nothing against RT or JCE or FCK or the fantastic mootools options....
cheers - For Professional Web-Development::
http://gws-studio.com
For Specialized Joomla Support:: http://gws-desk.com
For Specialized J-hosting:: http://gws-host.com
-
-
-
- GWS-Desk
- Sr. Rocketeer
- Posts: 132
- Thanks: 0
-
Daniel Chapman wrote:
I just checked the latest JCE and it uses mootools!Now that is positive! thank you for the suggestion...I am fully aware that they use mootiools in version 1.1.1 for compatibility reasons and the fact that the jquery was causing major issues. So Ryan replaced jquery and went for mootools...w ewill definitely test your solution ad reflect this with JCE-people.... Looks like interesting suggestion, thank you!
etc etc - For Professional Web-Development::
http://gws-studio.com
For Specialized Joomla Support:: http://gws-desk.com
For Specialized J-hosting:: http://gws-host.com
-
-
-
- MR RM Demmer
- Newbie
- Posts: 10
- Thanks: 0
-
Hi,
Just to clarify.
JCE does use mootools, but only by some JCE plugins, and within an index2.php page, seperate from the main page.
JCE Utilities, an optional mambot for JCE, uses JQuery and Mootools in a soon to be released version.
The problem seems to be with the mootools window.onDomReady function, as far as I can determine, or the incorrect use thereof.
Still investigating this.
btw. the error in IE (Operation Aborted) apparently occurs when an attempt is made by a script to access the DOM before the page has fully loaded.
Ryan.
-
-
-
- MR RM Demmer
- Newbie
- Posts: 10
- Thanks: 0
-
Some more info:
While rewriting my JCE Utilities popup script for Mootools, I noticed that the problem occurs when the Mootools Tips class is used. When this class is initialized, it creates a div and appends it to the body, which causes the error.
Hope this helps to shed some light on the problem.
-
Time to create page: 0.091 seconds