Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Jquery Library ClashesJquery Library Clashes
Previous
 
Next
New Post
2/16/2012 3:48 PM
 

Just a quick note to the community, and as a non-programmer, there should be some sort of standard developed by which all developers using javascript to defer to the DNN hosted switch, instead of trying to provide your own out of date version. I have had numerous third party clashes with modules lately and the problem seems to be getting worse by the day.

As a content engineer, I'm a prolific purchaser of DNN modules (DNN Corp. just check out my purchases in the DNN Store (Snowcovered) over the past three years for proof) and I love the assortment of competing products, but I'm being turned off by the finger pointing now going on amongst module vendors as they all say the other guys jquery library is out of date or stomping on the other's modules vendor's code. They need to standardize by using the hosted switch in host settings under DNN. At least I think that is the solution being a non-developer.

Will

 
New Post
2/16/2012 5:25 PM
 
actually the biggest issue I see is where module developers include direct links to their own jquery copies i.e. src include's. This can result in more than 1 copy of jquery which then breaks all jquery - instead module developers should be registering if their module requires jquery (http://www.dotnetnuke.com/Resources/Wiki/Page/jQuery.aspx ) that way clashes dont happen, and they benefit from the minimised/combined scripts work done as the client resource manager. As registration was introduced a couple of years ago, personally I would think carefully about using modules that did not use jquery registration as it would suggest the projects if not dead are certainly on the operating table

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
2/16/2012 6:31 PM
 

Yikes! So I should refrain from purchasing third-party modules from the DNN store? As a non-developer, how am I supposed to know if a particular vendor has registered their jquery library? Perhaps DNN  Corp. should start a certification program of some sort for vendors in its store, because these vendors modules are in deed stomping all over each other. I spent the past five days trying to get a very complex modules installed and a portion of the app wiped out all of the other jquery modules. It's quite frustrating.

Now that the new DNN store is built, the eco system or vendors needs to be cleaned up. The majority are one man bands, which is scary. :-) 

 

 
New Post
2/16/2012 10:56 PM
 
Willian, Demand that the module developers change. If DNN is including jQuery and the module is including jQuery, the module developer needs to change. I have spent alot of support time on this issue. It's mostly the UI that causes the biggest issue. I used the UI in one of my modules and it was a support headache because other module (and skin!) developers just included it willie-nillie. I don't care if you are a one-man-band or a 50 piece orchestra, it's easy to do it the right way, and the module developers just need educated. The new API is nice, but as with any new API changes, that means the module developers need to have multiple versions of their modules which is a pain. I think a good general rule is if they are running DNN5 or higher, don't include jquery, if they are running DNN6 or higher don't include UI.
Thanks
Mike
 
New Post
2/17/2012 2:19 AM
 
William Jeansonne wrote:

Yikes! So I should refrain from purchasing third-party modules from the DNN store? As a non-developer, how am I supposed to know if a particular vendor has registered their jquery library? Perhaps DNN  Corp. should start a certification program of some sort for vendors in its store, because these vendors modules are in deed stomping all over each other. I spent the past five days trying to get a very complex modules installed and a portion of the app wiped out all of the other jquery modules. It's quite frustrating.

Now that the new DNN store is built, the eco system or vendors needs to be cleaned up. The majority are one man bands, which is scary. :-) 

 

 No, not at all - i'm just suggesting you exercise caution e.g. there are a few extensions on the store which have not seen updates in 2+ years so the risk of them not having the correct jquery code is higher than a module with a regular or recent release (the store team have an enhancement request in to help filter out extensions that have not been updated in a long time)

As for a certification program, we tried that before but it had limited success -however we're reevaluating starting it again as since then the community size has grown substantially as have the number of customers willing to pay a little more for extensions (which would allow developers to pay a small price for certification knowing that there are more customers who would pay a bit more for piece of mind)


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Jquery Library ClashesJquery Library Clashes


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.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out