Major incompatibility issue (mootools causing havoc)
-
-
- Andy Miller
- Preeminent Rocketeer
- Posts: 9919
- Thanks: 96
- Web Kahuna
-
I have a suggestion, in the index.php file for element (for example), replace the:
window.addEvent('domready', function() {
with:
window.addEvent('load', function() {
This was the fix that seemed to resolve the issues with Vortex and slimbox, and might well help you with your issues.
-
-
-
- MR RM Demmer
- Newbie
- Posts: 10
- Thanks: 0
-
Thanks Andy.
I'm just going to rebuild the tooltip class.
I did this with JQuery, which by the way can produce the same error.
-
-
-
- Daniel Chapman
- Elite Rocketeer
- Posts: 1258
- Thanks: 0
-
I don't feel attacked at all nor was I meaning to be aggressive to you if it seemed that way.
I don't get angry very often and it certainly takes more than you have thrown at me. ;D
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/////
The attacking comment was direct at this comment you made towards someone else not me.
Protective mode are we?
The implication in this is that that anything they said was irrelevant because they were just protecting RT and not taking your request seriously. If this was not what you meant, then I apologize. But the rest of your comment basically supports this implication.
Anyway...
jmd wrote: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......
Some times things simply cannot be solved or worked around without you doing something. If mootools is the problem, then mootools is the problem, not RT templates. If you need to remove it, then you need to remove it. It may be your solution, and is not just running away.
jmd wrote:You don't need to go to wysiwig to use RT templates, you may need to do it to run mootools. The problem really is with IE though. (again as always it's ie >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......
)
jmd wrote: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!
But they don't work together, and the problem is mootools, JCE and IE
RT literally has nothing to do with this except that they have mootools in the template.
What can Andy do???
He cant change mootools, ie7 or JCE. The only thing he can do is remove mootools.
Which as I pointed out = suicide.
THAT may not be how YOU operate, but it's the reality of the situation. Andy hasn't updated mootools to my knowlege, merely extended it. Which are different things.
EDIT: maybe he can do something if his suggestion above works. In which case I humbly bow out as wrong. ;D
The handshake would do nothing, because the problem is -mootools- not RT templates.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.
It's like buying a computer with windows installed on it then asking the computer retailer to modify windows for you because it doesn't work with a particular program you want to use.
Because you are asking Andy to modify mootools. Which he has no control over.
Making requests is fine, but when the requests are for crazy things it's just not going to happen.
How was it wrong? You said if RT doesn't fix this problem you will have to move to other templates. What I was pointing out was that every other major template club now uses mootools. So you have no other template clubs to go to if you can't use mootools. Every other club's templates will give your users the same problems. Because the problems aren't in the templates.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
The problems are in mootools, JCE and IE.
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
I don't feel attacked, nor am I attacking. But I am -disagreeing- with you because what you are saying makes no sense to me.
If the IE/mootools/JCE front end combination doesn't work, how can RT possibly fix it? They have no control over any part of the problem, except that they include mootools in their templates.
If fish can't fly no amount of telling them 'WE don't work THAT way' is going to make them do so.
MR RM Demmer wrote: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.
RM: So the problem can be avoided by including a mootools script that doesn't include/use the tips class?
In which case jmd, when you download and try my idea -don't- include the tips class and see if that helps.
If this is the problem, then perhaps Andy can shed some on light on whether the bundle of mootools he uses includes this class or not.
Also RM, when you sue Jquery, do you use the $(element).something references or the Jquery(element).something references?
As you probably know, changing to the later will remove most JS library clashes with Jquery.
BTW don't get me wrong jmd, I am not trying to avoid the issue here, I would like it solved as much as the next man. I just think you are asking at the wrong place because RT has the least control of any group over this situation. - Last Edit: 17 years 11 months ago by Daniel Chapman.
-
www.ninjoomla.com
- The Ninjoomla Open Source Extension Club
Over 50 open source extensions and 100 videos to you build the site you want.
-
-
-
- MR RM Demmer
- Newbie
- Posts: 10
- Thanks: 0
-
But they don't work together, and the problem is mootools, JCE and IE
No. The problem is with the script that uses mootools. And IE, but thats another story.
RM: So the problem can be avoided by including a mootools script that doesn't include/use the tips class?
Not quite. The Tips Class won't be a problem until it is initiated.
Also RM, when you sue Jquery, do you use the $(element).something references or the Jquery(element).something references?
As you probably know, changing to the later will remove most JS library clashes with Jquery.
Mostly, but there is still a conflict with mootools, with some event stuff (unavoidable apparently). That is why JCE Utilities is going to have 2 js lirbary options - jquery or mootools
There is a solution to this. I will try and find it. Just got to get the new JCE updates out first.
-
-
-
- Daniel Chapman
- Elite Rocketeer
- Posts: 1258
- Thanks: 0
-
Not sure if there is, but if there anything can do to help you with either of those let me know.
MR RM Demmer wrote:But they don't work together, and the problem is mootools, JCE and IE
No. The problem is with the script that uses mootools. And IE, but thats another story.
I stand (partially) corrected.
EDIT: By the way, if possible I would include an option to use mootools as the library but to not include it when loading.
Because mootools has a habit of falling over if you try to load the libraries more than once. So it would be best to use the template mootools as it will be loaded first, and then have people replace their mootools script to include the correct libraries.
Nasty, I know but its the best option that I can see.
Perhaps if all the mootools using developers started listing the class dependencies in their mootools script it would make things a lot easier.
RT already does this, I will start doing it in my own JS work too i think. It will take a little bit of reeducation of web devs, but there isn't much else that can be done is there? - Last Edit: 17 years 11 months ago by Daniel Chapman.
-
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
-
Just to say thanks so far for most who have positively contributed to this turned out positive interaction. As you can see when one shifts focus and realizes that an issue exists and nothing stated is related to fantastic templates or to (for many) "da-best" editor JCE (or FCK) nor remarks are personal things can turn out positive....
@ Ryan: professional as always .........
@ Daniel: i will contact you through different channels anyhow
@ Andy: you guys keep on building these fantastic templates .....
thanks so far....
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
-
-
-
- Daniel Chapman
- Elite Rocketeer
- Posts: 1258
- Thanks: 0
-
Feel free to contact me jmd.
I would be happy to give you a hand, but obviously I can't promise anything. As I have even less to do with this than Andy ;D
But I do have a bit of experience with Mootools, and JS problems. -
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:
Feel free to contact me jmd.nothing to do with this issue.......
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
-
-
-
- MR RM Demmer
- Newbie
- Posts: 10
- Thanks: 0
-
EDIT: By the way, if possible I would include an option to use mootools as the library but to not include it when loading.
JCE Utilities 1.1.8 will have an option to choose either Mootools or JQuery.
Because mootools has a habit of falling over if you try to load the libraries more than once. So it would be best to use the template mootools as it will be loaded first, and then have people replace their mootools script to include the correct libraries.
JCE Utilities is a system mambot, it has to be. This loads before the template, so there isn't a way to determine if mootools has already loaded.
A possible solution - all Mootools versions updated to 1.11. This version includes a a variable definition:
var MooTools = {
version: '1.11'
};
So myabe we could add this to the top of the mootools.js:
function checkMoo(){
if(typeof MooTools != 'undefined' && (MooTools.version == '1.11' || MooTools.version == '1.10')){
return;
}
if(typeof Class != 'undefined'){
return;
}
};
checkMoo();
in other words - if Mootools is defined, that must mean that the rest of mootools is there too. The only problem with this is that the first version of mootools would need to contain everything - all functions and plugins.
I would suggest a generic mootools system mambot - kind of like what Phil Taylor did with xajax - containg the latest version of mootools, with everything, with packer compression.
Ryan. - Last Edit: 17 years 11 months ago by MR RM Demmer.
-
-
-
- Daniel Chapman
- Elite Rocketeer
- Posts: 1258
- Thanks: 0
-
A super compressed mootools weighs in a little under 50k. Not a huge amount, but could be noticable.
I actually have a few sites with the full version in place, minus a few classes I know I wont ever use.
JCE Utilities 1.1.8 will have an option to choose either Mootools or JQuery.
What I meant was a variable to tell the bot to load the library or not. ie use mootools but don't inlcude the script.
But this has me thinking. I suggest to jmd to remove the mootools from JCE, but it might be a better idea to remove it from the template and replace JCE with the 'heavy' one.
Or include the
if(typeof MooTools != 'undefined'){
return;
}
script in the templates.
It still requires either a full version of mootools or a custom one for each site(obviously impossible for mass distribution) -
www.ninjoomla.com
- The Ninjoomla Open Source Extension Club
Over 50 open source extensions and 100 videos to you build the site you want.
-
Time to create page: 0.065 seconds