Skip to content
Interactive Webs Deign Service
  • Home
  • DNN Modules
  • Blog
  • News
  • Contact Us
Interactive Webs Deign Service
  • Home
  • DNN Modules
  • Blog
  • News
  • Contact Us

jQuery Conflicts in DotNetNuke Modules–Advanced Login

  • by InteractiveWebs Team
  • Advanced Login Support, DNN Module, DotNetNuke Modules, DotNetNuke Support, DotNetNuke Tips, Mushroom Image Support

image

DotNetNuke can use jQuery to enable popup style and image rotator effects. These are great and a big improvements on technologies like flash. However it is not hard to find two separately coded jQuery modules that can cause conflicts when used on the same page as each other.

The Reason

The reason in most cases is that modules can be hard coded to use their own version of jQuery. (Think of jQuery as a plugin that is required for the code to load onto the web page).

The library that powers jQuery is often updated to include new features. Earlier version of DotNetNuke did not have any ability to load jQuery or reference it as “part” of the core of DNN.

So for any module written for early DNN versions, the library plugin for jQuery needed to be included or referenced to an online source like the free Google jQuery reference.

If two module are on the same page and calling different versions of jQuery into play, it is likely that one of the modules will conflict and fail to work correctly. Often it will be the more advanced or later built module that fails.

DotNetNuke Solution

The solution to this is to built a common core library into the core of DotNetNuke, and allow modules and other code to reference this single source when calling on the jQuery library for any reason.

DotNetNuke have included jQuery as an option in the host settings, to allow it to be loaded from there.

They run a release version of the jQuery library that is presumably updated with releases of DotNetNuke. The last version of DotNetNuke 5x shows this.

image

Modules can either call this library, or use their own library.

How Modules Use DNN version of jQuery or their Own version

Well developed code or modules will usually have a setting that allows you to reference the HOST DNN version of jQuery, or call into play the version that shipped with the module.

On our modules, we use a tab setting that looks like this:

image

If the “Load jQuery” is ticked, the module will use the jQuery library that is shipped with the module.

If the option is not ticked, the module will use the DotNetNuke included version of jQuery.

Best Resolution

When conflicts occur, the best way to resolve it is to ensure that both modules are referencing the exact same jQuery library version. The easy way to do this is to ensure that both modules are NOT using their own version, or in our case “Load JQuery” is NOT CHECKED. image

And, ensure that any other modules are also not referencing their own version of jQuery but are looking to the hosted jQuery. (Talk to the module developer on how to do this.)

Other Possible Problems

1. One of the modules may require a feature that is more advanced than the the hosted jQuery version. In this case, a later jQuery library will need to be referenced. To allow this to be done, DotNetNuke have allowed you to reference a URL for another version of jQuery.

For example, in our Mushroom Image module for DotNetNuke, the rotator effect requires a later version of jQuery than the last version of DotNetNuke 5x references. 1.4.4. To set a later version, you simply find an online resource like this Google hosted jQuery library:

http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js

And enter that URL into your HOST jQuery settings.

image

2. Another issue is that there may be a conflict in the jQuery script used to call the module actions. We have included the ability to customize the script used to reduce conflict.

image

Naturally this is an option for advanced users, and not all modules have this feature.

What is the Take Home Message?

When a conflict occurs, there is usually no “developer” at fault, but rather an incompatibility between the ways that the jQuery is being called. Don’t assume that the last module installed is to blame.

In most cases the conflicts can be resolved using the steps outlined above. This assumes that the modules installed have similar flexibility as we do in our modules.

Tags:jQuery

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Mornington Peninsula Pest Control
  • SmarterMail Email Setup on iPhone (Exchange) – Interactivewebs
  • Business Website with COVID-19 Safe Meetings
  • Website Auditor Reports Empty Title Tag
  • Setting up Mail App Windows 10 – InteractiveWebs SmarterMail

Recent Comments

  • InteractiveWebs Team on How to Stop Adobe Acrobat DC Displays Please wait while the document is being prepared for reading
  • Uddipan on How to Stop Adobe Acrobat DC Displays Please wait while the document is being prepared for reading
  • Joe Wilson on How to Stop Adobe Acrobat DC Displays Please wait while the document is being prepared for reading
  • Nikunj Kumar on ERROR The terminal server has exceeded the maximum number of allowed connections. RDP Solution
  • John on How to Fix Mac Microsoft Remote Desktop RDP Error Code 0x4

Archives

  • February 2021
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • May 2020
  • January 2020
  • August 2019
  • April 2019
  • December 2018
  • May 2018
  • April 2018
  • March 2018
  • January 2018
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • January 2017
  • December 2016
  • July 2016
  • May 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • October 2014
  • August 2014
  • June 2014
  • May 2014
  • April 2014
  • February 2014
  • December 2013
  • July 2013
  • May 2013
  • March 2013
  • January 2013
  • November 2012
  • October 2012
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • February 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009

Categories

  • Activity Emailer Support
  • ADFS
  • Advanced Login
  • Advanced Login Support
  • Analytics Report Support
  • Apple Mac
  • Bulk Emailer Support
  • CentOS
  • Cpanel
  • CRM
  • CRM 2011
  • CRM 2013
  • CRM 2015
  • CRM 2016
  • DKIM
  • DNN
  • DNN Module
  • DNN Outlook Social Connector Support
  • DNN Word Editor Support
  • DNS
  • DotNetNuke 6
  • DotNetNuke Modules
  • DotNetNuke Skins
  • DotNetNuke Support
  • DotNetNuke Tips
  • Dynamics 365
  • E-mail Tips
  • eLearning
  • Exchange Server
  • Feedback Designer Support
  • General Tips
  • Hyper-V
  • iOS
  • iPad
  • iPhone
  • Landrover Discovery
  • LH Pilot
  • Mautic
  • Mushroom
  • Mushroom Image
  • Mushroom Image Support
  • Mushroom Lite
  • Mushroom Lite Support
  • News
  • Office 365 Website
  • OpenCart
  • Photography
  • Pivot
  • Rants
  • SEO
  • Server Tips
  • Services
  • Silverlight
  • SmarterMail
  • SQL
  • SSL
  • Subscription Module Support
  • Support
  • TFS
  • Uncategorized
  • UsersOnline
  • UsersOnline Support
  • Web Tips
  • Websites
  • WHM
  • WHMCS
  • Windows 2012
  • Windows 2016
  • Windows 8
  • WordPress
  • Xcode
  • Zendesk

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org