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

OLEDB jet 4.0 driver In Vista 64bit / he 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine

Well i think you must be thankful for me specailly for this research i am really getting the solution after 6 month research that is how to enable the oledb jet 4.0 driver in vista, i read arround 100s of articles and maximum said that is not possible to enable it and ala bla well at the end i got the answer that is so easy Acctually that is correct that oledb jet 4.0 driver is not avaialble for 64 bit but if you run your IIS on 32 bit instead of 64 then Oledb jet will working fine Here are the steps Click on the Start > Program > Administrative Tool > IIS Management panel Select the Computer name Right click on the application pool and select properties Select "TRUE" in Enable 32 Bit Application by default it is false Then this problem will resolve if you need any assitance then feel free to email me rashidbilgrami@hotmail.com Regards Rashid Imran Bilgrami CEO Best visualization www.bestvisualization.com

How to convert and crack windows server 2012 from Evaluation to Full

Dear All This is a way how you Convert Evalution to Full Step1: Open CMD and run following command DISM /online /Get-CurrentEdition <edition ID> is like ServerStandard with out Eval Step 2: DISM /online /Set-Edition:<edition ID> /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula WINDOWS SERVER 2012 Serial Key Windows Server 2012 DataCenter: 48HP8-DN98B-MYWDG-T2DCC-8W83P Datacenter: Y4TGP-NPTV9-HTC2H-7MGQ3-DV4TW Standard: XC9B7-NBPP2-83J2H-RHMBY-92BT4 Standard R2: DBGBW-NPF86-BJVTX-K3WKJ-MTB6V Server Essentials: K2XGM-NMBT3-2R6Q8-WF2FK-P36R2 For Standard R2 here is a command For R2 its like that DISM /online /Set-Edition:ServerStandard /ProductKey:DBGBW-NPF86-BJVTX-K3WKJ-MTB6V /AcceptEula Regards

SugarCRM Footer Logo Remove & SugerCRM violation Message Remove

Hi Reader, Let us discuss about how to remove the SugarCRM Footer logo.. You all are aware of the power of the SugarCRM Tool and also must be very eager to remove the footer in order to make it look more professional. So below mentioned are some tricks for removing the footer from SugarCRM Community edition. 1)  O pen-modules/Administration/ updater_utils.php Add-exit() ; in between   function check_now()   and   return . any where By doing this u can remove 'powered by sugar crm' footer logo. 2) Go to  modules/Trackers/Tracker.php, line 128, in the 'logPage' function. Drop the 'echo' statement. 3) Now to root(Sugarfolder)\include\mvc\view\sugarview.php and modify the line array(show header => true, show subpanel => true...........and so on) and make the changes to showfooter=>true to  showfooter=>false Now how you remove the violation  Go to include /utils/ mvc_utils.php and remove the line or code b...