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.

ImageCompare with twentytwenty - lessons learned from a a No-Code DNN App

As you probably already know, I love no-server-code Apps. They allow admins/web designers to extend their DNN without requiring host-permissions and without risking the system stability. It also allows them to modify the extension with very basic capabilities. When creating the ImageCompare App (download heredemo here)...


...I ran into some common issues that you will have as well - and would like to share the lessons-learned here.

Common Problem #1 - Show-Hide Features without server code

Sometimes you'll have settings which should show/hide a feature. In Razor, you could easily write something like @(Content.ShowButtons ? "some CSS" : "other CSS"). This would work - but requires server-side code. So how to handle this without code? We have 2 options:

Solution 1: Using JavaScript

This is the "one size fits all" solution - as you can simply move all the logic to the client. It's not sexy though, but works. Since 

Solution 2: Using Neat CSS-tricks

My preferred solution is as follows:

  1. Assuming that we have a value like ShowButtons which can be "true" and "false", and that a "true" means show, a "false" means hide...
  2. Then create 2 CSS classes, one for show, and one for hide. Their names should be something like "app-compimg-showoverlay-true" and "app-compimg-showoverlay-false" each should have the correct show-hide rules included. In our example, the important line is
    .app-compimg-showoverlay-false .twentytwenty-overlay { display: none !important; }
    meaning that the .twentytwenty-overlay inside a .app-compimg-showoverlay-false should be invisible
  3. Then all you must do as ensure that this class is created in the right place, like this:
    class="app-compimg-left app-compimg-showoverlay-[Content:ShowButtons] twentytwenty-container"

That's the entire magic. It's clean, simple and easy to understand. I must admit though, that it takes some practice to actually come up with such a solution, but I recommend you try these things.

Common Problem #2 - Multiple Instances on One Page

Many JS-Tools have neat, simple demos which work if the tool is included once on the page. Most demos begin to fail or behave incorrectly when included more than once - something that's very common with DNN. For example, the demo-page for the App has three occurances like this:

This looks rather simple. The problem is, that some elements of the demo code cause problems. In this case, it was...

  • Show-Hide of the button-like labels "before" "after" is controlled through a CSS. using the provided demo-code, it would always show or hide these buttons, based on the last module of the page. This is because the original code was
    .twentytwenty-overlay { display: none !important; }
  • Button labels - again the last module would set all the labels. If they are all the same, that's ok, but often you want different ones. Problem is again the code like
    .twentytwenty-after-label:before { content: "[Content:AfterText]"; }
    .twentytwenty-before-label:before { content: "[Content:BeforeText]"; }

Solution #1 - Use JavaScript

Again the simplest version would be to implement JS. There are logical ways to do this, but again it's often not very sexy, causes FOUC and quickly makes something simple become a "programmers problem". I won't demo it here. 

Solution #2 - Create Feature Specific CSS

This is the identical solution to #2 of the previous problem. So instead of 
.twentytwenty-overlay { display: none !important; } 
you simply create a more complex class like 
.app-compimg-showoverlay-false .twentytwenty-overlay { display: none !important; }

This new class is "feature specific" meaning that you can now control enabling this feature simply by adding the class to the tag above. 

Solution #3 - Identify with ModuleID or EntityId

My favorite solution is to include the ModuleID and/or EntityId (the DB-Number of the presented information) in various CSS-classes. Here's how it's done in the Image-Compare App:

I hope you liked this and will give it a try yourself. I really want to encourage you to develop No-Server-Code solutions for DNN, as it will allow less-versed users (admins/web designers) to create amazing stuff!

With love from Switzerland

Good article, thanks for your share. However, I think it is not a easy thing to require a programmer to know both server side coding and client side design (css) well. So sometimes the server side code is also acceptable. For example, to hide something, we can simply write: divContent.Visible= false;. It is easy and straightforward. Wednesday, August 27, 2014 6:27 AM (link)

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