> Hello,

> I am building a plugin which loads in several 3rd-party libraries
> including jQuery 1.7 (and then executing some scripts with those 3rd-party
> libraries), and I am encountering an issue where any extensions which
> already use jQuery will cause the DOMReady event to fire prematurely, thus
> causing numerous errors.

> Is there a way to avoid this, such that the documentready event can be
> fired as per normally?

> Thanks in advance.

> Just to be a little more specific (as it appears I still may not have
> correctly diagnosed the problem), the 3rd-party libraries' methods are
> returning 'undefined' when called.

> For example, I have loaded in the chosen.js libarary.  When calling via
> console, this:

> $("select").not("#editor_selection, #lang").chosen()

> yields:

> TypeError: Object [object Object] has no method 'chosen'

>    1. arguments: Array[2]
>    2. get message: function () { [native code] }
>    3. get stack: function () { [native code] }
>    4. set message: function () { [native code] }
>    5. set stack: function () { [native code] }
>    6. type: "undefined_method"
>    7. __proto__: Error

> Once again, this problem only occurs when in the view of a component which
> uses jQuery.

> Thanks for any help.
> On Sunday, July 15, 2012 2:39:26 AM UTC-6, SonarEclipse wrote:

>> Hello,

>> I am building a plugin which loads in several 3rd-party libraries
>> including jQuery 1.7 (and then executing some scripts with those 3rd-party
>> libraries), and I am encountering an issue where any extensions which
>> already use jQuery will cause the DOMReady event to fire prematurely, thus
>> causing numerous errors.

>> Is there a way to avoid this, such that the documentready event can be
>> fired as per normally?

>> Thanks in advance.