Hello

I'm using JQuery (1.2.6) on a skin. Everything went fine until I upgrade to Dnn 4.8.4 and pass the SOLPartMenu to DNNNav control. The DNNNav menu works just fine but when I declare JQuery, the menu breaks. It seems that JQuery works on some function used by DNNNav but I'm not able to find what's happening exactly. IE just reports this error, which is pretty generic :

"this.container.parentNode" is null or not an object.

To reproduce this bug, simply add the JQuery code to any skin of DNNBlue for example.

< script type="text/javascript" language="javascript" src="http://code.jquery.com/jquery-latest.js" >< / script >

JQuery is actually being used on a critical project, we just can't don't use it. So, if someone found a way to remedy, I would be very gratefull.

Actually, we can't use JQuery any version with latest release of Dotnetnuke.

Cheers,

S.F.

Hello Ian,

Thanks for your answer, the jQuery.noConflict make it hot.

That's important to say that the conflict is an effect of the common use of the $ object in jQuery and the new dnnControls. When you use the jQuery.noConflict mode, jQuery changes his master sign from $ to jQuery (by default but you can surcharge the noConflict method to pass any name). As effect, you have to transform your plugins code to reflect this change.

For example :
$("body").addClass('DnnBody');
becomes
jQuery("body").addClass('DnnBody');

Thank you for your help Ian, let me know if I can do anything for you.

Cheers,

S.F.

jQuery is very usefull when end user experience comes at the very beginning of the project.

I'm experiencing another issue using jQuery. The JIT debugger is reporting an error. This appears on all developpers computers when I declare the jQuery. Error is reported as following in the Windows Event Viewer :

" An unhandled exception ('Launch for user') occurred in w3wp.exe [PID]. Just-In-Time debugging this exception failed with the following error: Debugger could not be started because no user is logged on. "

Are you experiencing the same issue ?

I may desactivate the JIT Debugger in all computers, but this isn't really a solution. Is someone understanding what's happening here ? Any way to remedy ?

Cheers,

S.F.