We tried that. But that seemed to undefine the 1.1 jQuery too, which was on the page. So none of the existing page jQuery stuff using $ worked anymore.
We had the line at the top of our script page. How does it know which jQuery to blow away and which to leave alone? Glen On 10/3/07, John Resig <[EMAIL PROTECTED]> wrote: > > > Yep, you can do .noConflict(true) which completely blows away both $ and > jQuery. > > So, in your case, you would do: > > var veryjQuery = jQuery.noConflict(true); > > --John > > On 10/4/07, Glen Lipka <[EMAIL PROTECTED]> wrote: > > We are making a jQuery+stuff script that will go on lots of random pages > > with unknown libraries. > > Some of those pages will have jQuery. (Various versions) > > > > If I am including our script last; what is the best way to make sure our > > script doesn't interfere with any of the existing page, including old > > versions of jQuery. > > > > Solution #1: We renamed jQuery in our script everywhere to be > veryjQuery. > > Solution #2: ??? > > > > Note: Solution #1 solved the problem, but feels invasive. Is there a > > noconflict() way to do this? > > > > Glen > > >
