Sunday, 20 April 2008 13:41 Last Updated on Friday, 24 December 2010 08:30
If you're trying to use FireBoard 1.0.4 and any YooTheme, RocketTheme, or any other Joomla templates or Joomla components that utilize the MooTools framework, you will find out that MooTools has a conflict with FireBoard's JQuery framework. In my case, when I tried to use Fireboard and Page YooTheme template together, my MooTools that came with the template became non-functional on the FireBoard forum page because it overwrote MooTools framework. Everything that uses MooTools framework, like styleswitcher, spotlight, slider, and pretty much the whole YooTools package threw errors not being able to find required functions. Thankfully, developers at JQuery implemented a really easy workaround with the noConflict() method. Unfortunately, nobody at YooTheme, RocketTheme, and FireBoard seem to know about this easy fix. I know this because I originally searched in their forums for hours for the fix, and they all just gave up, which was very discouraging for me at first, and I almost gave up. However, I knew more about the problem, and it was simple problem, and I was willing to try to hack the thing myself to make it work. Eventually, I found out about the noConflict() method that nobody at these forums suggested. I found out later that JQuery and MooTools forums were much more helpful, and have a much more of a "developer" community, whereas other forums I mentioned earlier have a more of a "customer-in-crisis" community with no developers to help them. In YooTheme's case, I was very disappointed with their lack of any real developers. There are few staff members that go around the forum and answer questions, but it seems like their job is just to tell their customers that there is no fix. Those staff members are probably not developers, but rather customer support.
Here is the fix with noConflict()
1. Open /syydemo/components/com_fireboard/fireboard.php
2. Find
// Add required header tags $mainframe->addCustomHeadTag('<script type="text/javascript" src="' . JB_JQURL . '"></script>'); $mainframe->addCustomHeadTag('<script type="text/javascript">
3. Add noConflict() methd below so it looks like this.
// Add required header tags $mainframe->addCustomHeadTag('<script type="text/javascript" src="' . JB_JQURL . '"></script>'); $mainframe->addCustomHeadTag('<script type="text/javascript"> jQuery.noConflict();
Here is an explanation of how noConflict() works. JQuery backsup $ variable when it starts loading and overwrites $ variable. noConflict() method simply replaces the current $ variable with backed up $. You need to do this at the end when JQuery is done with loading. The scenario with FireBoard and YooTheme is that MooTools first gets loaded to $ variable, then FireBoard comes and overwrites it, now when you add jQuery.noConflict() method, you are telling it to bring back its overwritten $ back. This method can go anywhere after loading JQuery. This fix will not only work with JQuery and MooTools, but JQuery and any other frameworks it may have conflict with. They can be fixed in a similar way. A helpful hint if this doesn't work is to check if you're loading JQuery first, and then MooTools. If that's the case, you will want to switch the loading points of these frameworks, so that JQuery gets loaded later. At the moment, JQuery is the only framework smart enough to back up things it overwrites. Their developers are smart enough not to assume the people are only going to one framework at a time. If you have any questions, leave a comment here, and I will try to answer.

By pichwayz , April 07, 2011
By linitux78 , June 12, 2010
please, can you tell me where to add this line : jQuery.noConflict();{/code} ???
in index.php of tempalte OR index.php of site ???
And where exactly ??
By fjh , April 19, 2010
Thanks!
By Web Development Surrey , January 19, 2010
Great tutorial,
I can use fireboard now,
Thanks for writing, most people don't bother.
By Best Registry Cleaner Reviews , January 11, 2010
By Mike Chapel , September 24, 2009
I had a conflict with my template of Joomla (itech_bd_edition) and Yootools. The solution was to include the code jQuery.noConflict(); at the index.php site, before the < / script > of the slideshow script.
That was all.
;)
By Neil , August 11, 2009
By John Merlino , April 18, 2009
Please help
JM
By Myrddin , January 26, 2009
http://preview9.awardspace.com/escacsgerunda.cat/gerunda/index.php?option=com_morfeoshow&task=view&gallery=1&Itemid=172
I've been trying to use the jQuery.noConflict with no success.
Anybody with the same problem?
Thanks.
By Pol , December 26, 2008
Ottimo lavoro davvero!!
GRAZIE GRAZIE GRAZIE!!! :D ;D
By jay , November 19, 2008
By Steve , November 05, 2008
Thanks again!
- Steve
By David , October 19, 2008
the effects stop working. I assume it must be a similar problem, but this time we don't have access to the php code to include the noConflict() invocation. Following your post, the solution should be to load Mootools before the Facebook api. However, I think that this is going this way:
Yi - Usuarios
var YtSettings = { tplurl: '/templates/yoo_shuffle', color: '', layout: 'left', fontDefault: 'font-medium', widthDefault: 'width-wide', widthThinPx: 790, widthWidePx: 960, widthFluidPx: 0.9 };
x
FB_RequireFeatures(["XFBML"], function(){ FB.Facebook.init("4f80521c7a5a997607a6ae117889f63d", "xd_receiver.htm"); }); Please, login
I'd be really thankful if you could help me with this problem.
Thank you (and sorry for so much html). Regards,
David.
By Arrawnt , October 18, 2008
Regards.
Arrawnt.
By Arrawnt , October 18, 2008
thanks!
By Marc , October 14, 2008
Neither 1.0.4 nor 1.0.5 RC2. Adding this line doesn't change a thing.
Maybe there is anything else??
I look forward your ideas. Many thanks in advance.
By John , August 30, 2008
off-topic!!
Im in love with your comment system!!! which 1 is it???
love
By manchester student , August 07, 2008
By Taryn , July 26, 2008
By localhost , July 22, 2008
Are these original solutions ? I have seen the same on a few forums, eg YOOtheme, BOJ etc, that are dated before yours, either way someones fooling someone. You however claim to have discovered the solutions.
Anyways thanks for making the webspace available for sharing this with the community.
By Jimmy , July 17, 2008
By lebaleze , June 25, 2008
It works fine whith Joomla 1.5.3 and Yootheme beyond
Perfect fix. ;D
By Juan Manuel Verges , June 11, 2008
By soundbite , May 31, 2008
It's really not a problem for front-end users. The problem is with it's effect on my life when I'm doing administrative stuff with my site all day. Anyhow, it's aggravating to have this happen and not know where the problem is coming from.
If I don't have the back end and front end open in different browsers, my browser starts chugging away like a mad man on the front end trying to process scripting...(in either IE or Firefox). Finally it asks me if I want to continue or stop processing the script. This happens regardless of what computer I use (Core Duo and Pentium Mobile). It's happened on several versions of Joomla 1.5 installed on different servers for different sites. It's even happened when I mistakenly left the demo.yootheme.com site open in a tab while I was working in the backend of a site. Eventually my browser got bogged down with scripting. Firebug gives me an error in yt_tools.js (forget exactly the message right now).
I knew that yootools uses mootools, but I wondered if maybe the Joomla back-end was using JQuery, thus causing the conflict. I guess from what you're saying, this isn't the case. Oh well!
By soundbite , May 31, 2008
I've use the yootheme Seasons template in Joomla! 1.5.3 and consistently have problems with yootools scripting going nuts. I found that after about a half-hour of keeping open both the front-end (which uses yootools) and the back-end Administrator (which uses...what?) you start getting script problems in your browser (IE or Firefox).
However, here's what's weird--if you open the Administrator section in one browser (e.g., IE) and the front-end in another browser (e.g., Firefox), the scripts don't spaz out. The only way I've found around this is to disable Javascript in the YooTheme template settings (which is obviously pointless).
Do you think what you are talking about here has something to do with that conflict?
BTW: Your description of the yoothemes forum is spot-on.
