Javascript conflict

[joshua]

On pages with a 'View Cart' link (specifically the included link to box.js) I start getting an error from another function.



I've updated the version of jQuery being used (1.3.1 to 1.4), checked the documentation and examples for scrollTop(), and tried changing the order that my javascript files show up in the document (a solution that has worked for other problems) . So far nothing eliminates the error other than removing the e-junkie javascript.



The function and error can both be seen here:

http://pastie.org/789547





Does anybody have any ideas or suggestions?

[E-junkie_Guru]

Could you provide the URL of a live page where you get this error using our View Cart code referencing the box.js script? Also mention which browser(s) you've tested with that produce the error.

[joshua]

The proper behavior can be viewed at:

http://www.astontechconsult.com/ebooks.php

the problem can be seen at:

http://www.astontechconsult.com/ebookstest.php



Both pages are identical except for the inclusion of the 'View Cart' button and its associated javascript.



On pages without the button effects.js runs correctly and scrolls the page in Firefox 3.5.7, Opera 10.10, Safari 4.0.4, IE8, Chrome 4.0.249.78, and in IE6 and 7 running under IETester (http://www.my-debugbar.com/wiki/IETester/HomePage). Scrolling does not occur on pages which do include the 'View Cart' button.



I'm able to view the error notice linked in my first post using Firebug in Firefox and Dragonfly in Opera. The problem has also been reproduced on my local development server (XAMPP).



Any help is appreciated.

[E-junkie_Guru]

We'll need to ask Development to look into this, as it's a bit beyond Support's familiarity with how our software is programmed.

[joshua]

Thank you, I look forward to hearing what development has to say.



Fortunately the first premium items aren't ready to go up yet so there is time to find a solution. I'll also start looking for an alternative auto-scroll function as a contingency.

[joshua]

Is there any news about what is causing the problem or if there may be a resolution from support of developments end?

[E-junkie_Guru]

Hm, I'll have to prod Development to see if they've been able to look into this or find a solution yet.

[joshua]

Thank you.

[joshua]

I've created a work around for this particular case by replicating the original jQuery script with the Prototype framework.



While I appreciate your efforts to help and understand that this problem may be one that needs to be delegated to the development team I am extremely dissapointed that it has been two months without any updates about if the problem is being worked on or what, if any, progress has been made. This combined with what appears to be poor isoalation of e-junkie's javascript from other scripts on a page means that I'm going to be much more cautious about using e-junkie in the future.

[E-junkie_Chef]

Joshua, I am sorry that we dropped the ball on this one. A couple weeks ago we have made some changes in our script which should make it "conflict proof".



The way it works now, if there is a jQuery include present before you include box.js, and its version is greater than 1.2.3 (which is the jQuery version we use), then our jQuery object is only referenced as ejejc_jQuery and your jQuery object is available as jQuery.



You can also "force" this behavior by setting EJEJC_PLAYNICE=true; in EJEJC_config function.



All the conflict resolution code can now be plainly seen in box.js.



Do let us know if you still face an issue and we'll promptly address it.