Opt In Email 4.0
'Relationship Building' and 'Communication' are two essential nuts and bolts for a business to prosper. This module allows you to bridge both of these and easily generate continuous awareness of your web site, products and services. Your prospects and customers will greatly appreciate this featur
Live Content v1.6.1 :: Web 2.0
Live Content uses Web 2.0 approach to provide a Rich User Interface and streamlines content presentation by overlaying content on current page. Overlay images, videos, audio, text/html content, flash, dotnetnuke modules, and external content. Experience the demo...
XMod 5.1
Version 5 of the perennial best-selling tool for creating data-based solutions in DNN without custom programming. This version focuses on greater flexibility, expandability, and ease-of-use.
Open-DocumentLibrary v3.0
Powerful, Ajax Enabled, Easy to Use. Document Management has never been better. Open-DocumentLibrary allows DotNetNuke users to share and manage documents in a flexible, intelligent way, offering granular control over Folder and Document access.
Ultra Video Gallery 2.4
Ultra Video Gallery is a brother product of Ultra Media Gallery, UVG allows you to add videos in various format and automatically convert them to flv format, you also can add videos from embed code and play them in our integrated flash video player.
Gloss // ALL COLORS! skin // XML Flash // W3C CSS XHTML1.0
Gloss is the first ALL COLORS! skin, featuring a powerful XML-based flash and being 100% W3C CSS XHMTL1.0 compliant. Tune it yourself on the fly, changing colors, backgrounds, containers, text color and size, width and more! Brilliant!Available for DNN4 and DNN5
Active Forums
The award winning discussion forum and community solution for DotNetNuke is now even better. When you need to build the best community site, you need the best module, Active Forums!
Minimalist by Evan O'Neil - ALL NEW !
ALL NEW ! - Minimalist includes skin packs in 12 great colors. Each color has Flat, Gradient and Glass versions. Feature rich XML Flash header, perfect for just about any purpose. 9 Different menu options in each skin pack; 3 horizontal menus, 3 vertical menus and 3 all-new Twin level menus . . .
Document Exchange 5
Edit documents directly on your server. The premier document management solution for DotNetNuke (DNN). Index contents of documents. Share documents across your portal and avoid duplicates. Revised and flexible UI. Extensible architecture.
Ultra Media Gallery 5.4
Ultra Media Gallery is the most popular photo gallery and media gallery solution for DotNetNuke, UMG offers 10 different flash player to browse your gallery with completely different user interface experience.
I'm struggling with the Dynamic Registration documentation.
For instance, there is a very short paragraph about core DNN fields and Dynamic Fields, but it doesn't say how many Dynamic Fields can be mapped to Core fields.
What do I do with the other dynamic fields once I've mapped a single core field to a dynamic field?
The documentation started off like a well written walkthrough/tutorial, but as you try to get past the repetition of screenshots, the doc content seems to wane quite a bit.
Am I just thick or what? Perhaps it's just me!
Mike, Hi. Much of this has to do with the fact that core fields (and core extended fields) have changed throughout the history of DotNetNuke and therefore Dynamic Registration as well. The real purpose of the core field integration is to keep your Dynamic Registration in sync with DotNetNuke. This isn't necessary except in cases for example where you might use another module to import users and you want them to have their DNN data displayed within Dynamic Registration or if you used the core manage users area or somehow modified the core data without using Dynamic Registration. Because of this we allow the ability to 'link' core fields directly with dynamic fields. This means that every time the user saved their data its saved in both the Dynamic Registration tables and also the core tables. If a field is linked and you change the core fields it will pull those values in instead of Dynamic Registration etc... Basically you can link/map as many dynamic fields with core fields as you would like. If you decide not to map a field there is no harm in doing this, only if you wanted to export user data or access that data within the core somewhere and then you might have problems. Modules such as our Dynamic User Directory module support both accessing the core data and the Dynamic Registration data directly so it wouldn't matter for modules like that example but it might matter if you were using another 3rd party tool to manage users with etc.. Hope this helps with understanding the purpose of mappting DNN fields with Dynamic Fields etc... -Chad