New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesDNN 6.1 and jquery plugins errorsDNN 6.1 and jquery plugins errors
Previous
 
Next
New Post
11/2/2011 10:41 AM
 
Hello,
after upgrading to 6.1, I'm getting tons of javascript "jquery not available" errors on any external jquery plugin I try to use.
Debugger breaks on last line of each plugin, for example:

;(function($) { 
  $.cluetip = {version: '1.0.6'};
[..........]
})(jQuery);


Other jQuery code runs pretty good.
I suspect this is due to the new clientDependency controls/functions, that is: in order to let any module using external jQuery plugin to work properly on 6.1, must I update it to use the new APIs? Or is there a way to let my existing modules run properly on 6.1?

Thanks for any help,
al.
 
New Post
11/2/2011 11:30 AM
 
Hey Alberto,

There shouldn't be anything requiring you to move to the new API. Had you upgraded to 6.0x previously or is this your first move to 6.x?

Also - can you locate the exact place in the document that jQuery is being loaded? Is your failing JS located below that or above it?

I'd be glad to help troubleshoot if you can share any more info or a link to the site (if public).

Thanks,

Ian

Software Engineer
Co-Founder, dnnGallery
Stack Overflow: Ian Robinson
Twitter: @irobinson
Linked In: Ian Robinson
 
New Post
11/2/2011 11:40 AM
 
Ian, 
thanks for your answer. I'm currently running DNN 06.00.02 on that site (private), and have no issues there. I tried the upgrade this morning and then rolled back, so don't have it ready for testing now - but will do more tests briefly.

With 06.00.02 I see jquery.js is loaded before any other .js resource, but did not check if the order was the same with 6.1 (good point to start from).
I also must say my errors were with modules built with XsltDb, but don't think this is the problem.
I'm investigating further!

Thank you,
al.
 
New Post
11/2/2011 12:16 PM
 
Ian,
uh uh my fault, you were right: the error is due to the position where my .js files are included!

With XsltDb you have three options (page, form, module) to specify where to put inclusions: I'm using page, but could verify with a quick test that moving to form or module solves my problem.
Something must have changed with 6.1, but using the correct location solves this issue.

Thank you!
al.

 
New Post
11/2/2011 1:12 PM
 
That's interesting - jQuery is still loaded in the head as it was before, but you're right, something must be different there!

Glad you got your specific issue resolved though.

Take care,

Ian

Software Engineer
Co-Founder, dnnGallery
Stack Overflow: Ian Robinson
Twitter: @irobinson
Linked In: Ian Robinson
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesDNN 6.1 and jquery plugins errorsDNN 6.1 and jquery plugins errors


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.