DotNetNuke will use jQuery help popup model along with picture rotating results. These are good plus a massive improvements with systems such as flash. On the other hand it's not difficult to find two separately coded jQuery modules that may cause conflicts when utilized on the same page while as each other.
The reason
The reason typically is actually which modules might be hard coded to use their version of jQuery. (Think of jQuery as a plugin that's needed for your code to insert onto the web page).
Your library which powers jQuery is often updated to include new capabilities. Sooner version of DotNetNuke do have no capacity to insert jQuery or even reference reference it as “part” of the core of DNN.
Consequently for almost any component published for early DNN types, this library plugin for jQuery would have to be bundled or referenced to an online source like the free Google jQuery reference.
If a pair of module are generally on the same site and calling various types of jQuery into play, it is likely which one of several modules will certainly discord and also neglect to perform appropriately. Often it's going to be the harder advanced or even later on built module which fails.
DotNetNuke Solution
The treatment for this is to built one common core library into your core ofDotNetNuke, and let modules along with other code to reference this specific single source when calling on the jQuery library for every reason.
DotNetNuke have included jQuery as an option inside the host adjustments, to allow it become loaded from there.
They run a release version on the jQuery library that is certainly presumably kept up to date with releases of DotNetNuke. The past version involving DotNetNuke 5x show this.
Modules can easily either call up this library, or use their own library.
How Modules Use DNN version of jQuery or Their Own version
Well created code or perhaps modules in most cases have the setting that permits you to reference this HOST DNN version of jQuery, or call into play in the version that shipped with the module.
With our quests, we work with a tab placing that seems as if this:
If this “Load jQuery” can be ticked, the module uses the jQuery library that may be shipped with the module.
If the option is just not ticked, the module uses the DotNetNuke bundled version associated with jQuery.
Greatest Resolution
As soon as conflicts happen, the best way to resolve it's in order that both quests are referencing the same jQuery selection version. The quick way to get this done is in order that both modules are certainly not using their own version, or inside our case “Load JQuery” is just not CHECKED.
And, ensure that any some other modules are also not referencing their own version associated with jQuery but need to this hosted jQuery. (Talk towards the module developer on how to get this done. )
Other Possible Troubles
1. One of many modules may need a feature that may be more advanced compared to the the organised jQuery version. In that case, a afterwards jQuery library must be referenced. Allowing this to be done, DotNetNuke include allowed that you reference the URL regarding another version of jQuery.
One example is, in our Mushroom Image module regarding DotNetNuke, the rotating effect requires a later version of jQuery compared to the last version of DotNetNuke 5x recommendations. 1.4.4. To set a afterwards version, you just find a online resource this way Google organised jQuery selection:
http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js
And also enter that will URL into your HOST jQuery adjustments.
a couple of. Another issue is that there could be a conflict in the jQuery script employed to call this module behavior. We include included the ability to customize this script employed to reduce clash.
Naturally this is an selection for innovative users, and not all quests have that feature.
What's the Get hold of Message?
Each time a conflict occurs, there is generally no “developer” to blame, but alternatively an incompatibility involving the ways which the jQuery will be called. Don’t assume which the last element installed is to blame.
In most cases the conflicts can be resolved with all the steps outlined above. This assumes which the modules mounted have similar flexibility once we do inside our modules.
FREE ASP.NET Hosting for DotNetNuke Recommendation
ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $0. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.