appears blame cart code comfortable configured conflict confusion createelement default doubt download easily error event example framework function help indicated issue javascript jquery learn loading mode necessary onload perfectly pointing problem replace result return script software solution solve subsequent suggesting tag team upload variable verified view wait

I'm having a little difficulty getting E-Junkie to work under IE7, and there appears to be a conflict between Mootools and jQuery: if box.js is loaded, subsequent mootools code fails with an error pointing to this line:

return $.element(this.createElement(tag)).set(props); suggesting that there is some confusion with the $ function.

I've read about jQuery.noConflict(), and am now executing that onload of your box.js script:
new
Asset.javascript('https://www.e-junkie.com/ecom/box.js',
{onload: function() {jQuery.noConflict();}});

I have verified that the onload function is executed by IE. If box.js is not loaded, I do not get the above-mentioned error. I tried loading box.js as indicated in the 'view cart' code with the same result.

Our code (box.js) uses jQuery in noconflict mode by default and we use "jQuery" instead of $.

I think the following solution from
http://groups.google.com/group/jquery-en/browse_thread/thread/ 9737e52028077d5c/f4a45f44c44bb3fa
might help:

"I found a solution that works perfectly. I'm the live example that we need sometimes to use the both frameworks. I'm develop all my projects in jQuery, cause I learn more easily and feel more comfortable with it. Nothing to do with Mootools, with is a beautiful framework too... But I need the fancy upload to work and is just possible with Mootools, I make everything, but doesn't work because the conflict with the variable $event. I solve this issue by getting the mootools download with no compression, use a software like aptana, dreamweaver, or even notepad to replace all occurrences of $event to $event2 for example, and compress
the library after it. This way, the two frameworks works perfectly, since the use of jquery with noConflit its configured. I hope this works and soon I will develop this fancy upload for jquery to don't have to use both. Its a shame for the mootools team wait to Jquery solve this
problem that noboby its blame... its just convention... why just simple replace $event for $mootoolsEvent or $mooEvent for example??? Sometimes its necessary use both, no doubt.."