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!

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.

Mobile Device Detection and Redirection Improvements Coming Soon


With mobile device usage expected to eclipse traditional desktop usage by 2015, companies worldwide are looking for ways to adapt and to provide personalized, relevant experiences to site visitors on all types of devices. In response to this market demand, in November 2011 we introduced an exciting new platform capability as part of DotNetNuke 6.1 - mobile device detection and redirection management. This announcement was made at our annual user conference, DNN World, and it generated a ton of excitement within our ecosystem.

Device detection provides the ability to determine the type and characteristics of a device being used to browse a website. Once the device is identified, it is possible to make intelligent decisions to provide an optimized experience to the site visitor. This could be as simple as redirecting visitors to an optimized landing page or mobile-optimized site, or it could involve more sophisticated adaptive rendering or responsive design where the website customizes the content being served based on device characteristics.

Device detection is made possible by a Device Description Repository (DDR) which is basically a database of all known devices that provide connectivity to the Internet. In DotNetNuke 6.1 we included a DDR known as WURFL which at the time was available under a compatible open source license. However in the months since, the founders of WURFL decided to change its licensing model, which meant that we were forced to find an alternative. We evaluated a variety of solutions and ultimately concluded that the DDR offering from provided the highest quality device information while at the same time providing the flexibility to accommodate our business needs. is based in the United Kingdom and has over 25 years management expertise in developing and managing mobile web services. Their services are used by thousands of websites and currently support over 170 million device visits every month. Through strategic relationships with device manufacturers and other mobile data providers, they are able to maintain an extensive database of device and mobile browser characteristics. has distributed an open source version of its Lite device data and APIs on for the past 2 years.

In the upcoming DotNetNuke 6.1.5 release, we will be delivering a fully integrated DDR solution based on As part of this integration there are some exciting new features which will be available to both Community Edition and Professional Edition users of the platform.


All editions of the DotNetNuke platform will now have a Device Detection Management feature available on the Host menu. This feature provides information about the Device Detection Repository, including which version of the data is currently installed and the number of properties supported.

Community Edition users will have the Lite device data installed by default. The Lite data provides access to some basic device properties such as whether or not the device is a mobile device, and the screen resolution in terms of width and height in pixels. The Lite data is expected to be updated quarterly, with the latest public version available on distributed with Community Edition on an ongoing basis.


In order to take advantage of the upgraded device detection capabilities, the Site Redirection Management feature originally introduced in DotNetNuke 6.1 has been back-ported from Professional Edition to Community Edition. This feature is available on the Admin menu and allows you to create redirection rules that route devices to landing pages or mobile-optimized sites.

Community Edition users will also have the ability to upgrade their Lite device data to the Premium data option. They can do so by browsing to the product listing on the DotNetNuke Store and purchasing a license key. The Premium data will be available for $360 per instance per year ( the same subscription licensing model as is used in the DotNetNuke Professional Edition product ). Once the license is activated, the customer will have access to over 100 device properties with real-time updates of the device data downloaded automatically from the service.


DotNetNuke Professional Edition customers will also get access to the Premium data at no extra charge ( a $360 value per year ). This includes access to all device properties and the automatic updates, which are critical for any business which is serious about providing an optimized mobile experience. For example, the usage of tablet devices has really exploded over the past year and the Premium device data includes an IsTablet property which allows customers to identify and optimize the experience for tablet users.

One item I should also note is that if Community Edition users of DotNetNuke 6.1 were utilizing some of the more obscure device properties through the API, it is possible that the device detection logic will no longer behave as expected. This is because the Lite data only contains a minimal set of device properties as compared to the WURFL data we were distributing previously. In order to correct this issue, you will need to upgrade to the Premium data.


There are currently no comments, be the first to post one.

Comment Form

Only registered users may post comments.


Aderson Oliveira (22)
Alec Whittington (11)
Alessandra Davies (3)
Alex Shirley (10)
Andrew Hoefling (3)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (37)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Bogdan Litescu (1)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (213)
Chris Paterra (55)
Clint Patterson (108)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (181)
Daniel Valadas (48)
Dave Buckner (2)
David Poindexter (12)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (80)
Francisco Perez Andres (17)
Geoff Barlow (12)
George Alatrash (12)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (274)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Kelly Ford (4)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matt Rutledge (2)
Matthias Schlomann (16)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (40)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Oliver Hine (1)
Patricio F. Salinas (1)
Patrick Ryan (1)
Peter Donker (54)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Sacha Trauwaen (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott Schlesier (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Steven Fisher (1)
Timo Breumelhof (24)
Tony Henrich (3)
Torsten Weggen (3)
Tycho de Waard (4)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (180)
William Severance (5)
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out