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

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesDNN7 - Extending Existing ModulesDNN7 - Extending Existing Modules
Previous
 
Next
New Post
10/24/2013 8:40 PM
 

The entire DNN core is open source - and as such if you are willing to get your hands into the c# code there is nothing that cannot be modified.  However, that does come with a future compatibility proviso - if you change the API or edit a core module - then you will need to plan around keeping your custom modules compatible with future updates to DNN itself.

In most cases - what people do - is make a clone or copy of the existing core module - and use that as the base for your modifications while leaving the API layer alone.

Over the years we have built a number of custom sites based on this workflow - and they have evolved successfully from as far back as dnn 2.0 all the way thru to the current version - yes at times some custom modules have required a rethink or patch to ensure compatibility with new dnn core features - but the way the DNN api legacy calls system is maintained meant for the most part that things just continue to work.

Westa

 

 
New Post
10/27/2013 8:23 PM
 

Thanks Wes.

Definitely sounds like an option. Clone existing module and make changes to the cloned modules as opposed to the core framework. That way upgrades are not effected. Problem in my case there's a fair bit of changes including a lot of the profile information comming from another DB. Will have to have a look at what's the best option.

 

   

 
New Post
10/27/2013 8:37 PM
 

Thanks matthias for providing the licensing information.

 

 
New Post
10/27/2013 9:17 PM
 

I would work out what elements of the profile are needed inside DNN and what elements are not.

You can extend the core DNN profile fields to include any number of additional elements - which it will show automatically in the user profile etc.

Alternatively - we in the past have found it relatively simple to create a custom profile module that shows just the elements we need - and which pulls in data from other tables as well.   The advantage of this approach is that the data can be updated back into the other tables and not just into the DNN profile fields.

Westa

 

 

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesDNN7 - Extending Existing ModulesDNN7 - Extending Existing Modules


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