Skip to main content

DNN Skin Tokens

Dotnetnuke skin tokens - adding functionality to your DNN skins

The Dotnetnuke skin tokens are text placeholders used for inserting the dynamic content of Dotnetnuke into the HTML of the skin.

[ACTIONBUTTON]

This skin token defines the placement of the icon and text link for specific actions on containers such as edit and delete. This skin token uses the XML file to define which control it is and the options available include:
  • Add Content
  • Edit Content
  • Syndicate Content
  • Move Up
  • Move Down
  • Delete Module
  • Module Settings

[ACTIONS]

This skin token defines the placement of the dropdown menu within container skins.

[BANNER]

This skin token defines the placement of banner ads within the skin design.

[BREADCRUMB]

This skin token defines the placement of the breadcrumb generated for the current page. The position of the page is defined by its placement within the navigation.

[CONTENTPANE]

This skin token defines the placement of the content areas within the DNN skin. Multiple instances of this token can be used to create variations in layout such as 1, 2, or three columns and unused panes are automatically assigned a CSS class so they can be "hidden" or "collapsed" from the layout.
When using multiple [CONTENTPANE] skin tokens, each instance must be differentiated by a number e.g. [CONTENTPANE:1], and this is used with the XML file to define individual settings for each.

[COPYRIGHT]

This skin token defines the placement of the copyright notice for the website.

[CURRENTDATE]

This skin token defines the placement of today's date.

[DOTNETNUKE]

This skin token defines the placement of the Dotnetnuke copyright notice.

[DROPDOWNACTIONS]

This skin token defines the placement of a dropdown list of the module actions.

[HELP]

This skin token defines the placement of the help link which, when clicked will load the visitors email to send the administrator of the website an email.

[HOSTNAME]

This skin token defines the placement of the text and a link to the host details as defined in the host settings of the DNN portal.

[ICON]

This skin token defines the placement of an icon for use in a container skin. The icon is set in the module settings.

[LANGUAGE]

This skin token defines the placement of the Dotnetnuke language selector for use within multilingual websites.

[LINKACTIONS]

This skin token defines the placement of a set of links representing the actions of a module within a container skin.

[LINKS]

This skin token defines the placement of a flat collection of site links, often seen in the footer of skins to re-iterate the top level navigation. Settings in the XML file determine the relationship between these links and the current page.

[LOGIN]

This skin token defines the placement of the login and logout links for the website.

[LOGO]

This skin token defines the placement of the website logo as defined in the site settings of the website.

[NAV]

This skin token defines the placement of the navigation for Dotnetnuke. It is advised that this token be used instead of the [SOLPARTACTIONS] token as it is more up-to-date and the solpartactions provider is no longer supported.

[PRIVACY]

This skin token defines the placement of the privacy link within the skin design.

[SEARCH]

This skin token defines the placement of the search box within the skin design.

[SIGNIN]

This skin token defines the placement of the username and password sign-in controls.

[SOLPARTMENU]

This skin token defines the placement of the old menu provider for Dotnetnuke. This still works for backwards compatibility of skins however it is no longer supported and it is advised to use the [NAV] skin token and menu provider instead.

[SOLPARTACTIONS]

This skin token defines the placement of the dropdown menu for container actions such as edit content, delete content and more. It is advised that this skin token is no longer used and replaced with the [ACTIONS] token

[STYLES]

This skin token is used to insert IE specific style sheets.

[TERMS]

This skin token defines the placement of the terms link within the skin design.

[TEXT]

This skin token is used to insert portal specific text within the skin.

[TITLE]

This skin token defines the placement of a module title within a container skin design.

[TREEVIEW]

This skin token defines the placement of the treeview style menu.

[USER]

This skin token defines the placement of the register and user account links within the skin design.

[VISIBILITY]

This skin token defines the placement of the plus and minus controls within a container skin design.

Regards
Best visualization
http://www.bestvisualization.com

Comments

Popular posts from this blog

RegisterStartupScript updated way to right Java script JS (Javascript) in code behind also work with update panel

Dear All
RegisterStartupScript is obsolete now the new way that works with update panel  is given below its is code behind file code also

VB Code Dim csname1 As String = "PopupScript"
Dim cstype As Type = Me.GetType()
Dim cs As ClientScriptManager = Page.ClientScript
Dim cstext1 As String = "alert('Your message');"
cs.RegisterStartupScript(cstype, csname1, cstext1, True)

C# Code
String csname1 = "PopupScript";
Type cstype = this.GetType();
ClientScriptManager cs = Page.ClientScript;
String cstext1 = "alert('Hello World');"; cs.RegisterStartupScript(cstype, csname1, cstext1, true);
I hope it will help you also 
Regards  Rashid Imran Bilgrami

Calling LoadLibraryEx on ISAPI filter “C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_filter.dll” failed

Dear Readers
if you get the error

Calling LoadLibraryEx on ISAPI filter “C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_filter.dll” failed


Here is the solution 
Get a command prompt in administrator mode and go to C:\Windows\Microsoft .NET\FrameWork64\v4.xxx
and run aspnet_regiis -r. This will re-register the right libraries. It has happened twice already to me.
For other frameworks (32 bit or other versions of .net make sure you go to the correct folder (i.e. Framework/v2.xxx, etc.)

xxxx is the the number which is present with the folder name so i suggest you guys to check the folder name in your directory

If "run aspnet_regiis -r" is not working and if you get the error run is not recognized command then just type " aspnet_regiis -r" it will run fine

Reason of problem
Your asp.net frame work has been change may be you have install the lower version on the higher version or may be because of any reason you have register another version in your IIS, in my cas…

Multi Language Website In DNN Or Content Localization in DNN

Dear Readers
Before that when we create the Multi Language website in dnn we always create two portal but with DNN 5.x version you will use the language resource for creating multi language website website

You are facing two major challenges to create Multi language website
1) Translation of the DNN controls in to local language
2) Translate your own pages navigation or menu in to multi languages
3) Translate your own custom content in to local language
4) Translate your custom modules in to the local languages

Lets start with the first challange

Challenge 1: Translation of the DNN controls in to local language 
This is an easiest part, you can follow the steps achieve this challenge

1) Login with your host/Admin  account
2) Go to the Admin / Languages
3) Click on ADD Languages
4) Select the language that you need and Add it
5) You will see now two languages in your language section
6) With the list you will see the three option

Static Resources
System | Host |Site

7) you can click on t…