Skip to main content
Version: 1.27 (Current)

Preparing for Upcoming Changes in Token Usage in Page Themes

Audience: Developers, Administrators, Citizen Developer

Skill Prerequisites: Tokens, Themes, DNN

Overview​

With the upcoming Plant an App release 1.28, significant changes are being made to how tokens are used within themes. This article serves to inform users about these changes and provide guidance on how to prepare.

What's Changing in 1.28?​

In version 1.28, the methods previously used to integrate tokens in themes will be replaced with a new streamlined approach. This update is essential to ensure compatibility and improve the performance of themes. Understanding these changes and proactively updating your themes can prevent the pages from rendering errors post-upgrade.

Current Methods that will not be available in 1.28​

In version 1.27 and lower, tokens in themes can be embedded using one of these methods:

  1. Using the Skin Object:

    <%@ Register TagPrefix="MyTokens" Namespace="avt.MyTokens.Core" Assembly="avt.MyTokens.Core" %>
    <MyTokens:Tokenize runat="server">
      Hi [User:FirstName]
    </MyTokens:Tokenize>

  2. Alternative Skin Object:

    <%@ Register TagPrefix="Paa" TagName="Token" Src="~/DesktopModules/DnnSharp/MyTokens/SkinObjectReplacer.ascx" %>
    <Paa:Token runat="server">
      <content>Hi [User:FirstName]</content>
    </Paa:Token>

New Method in 1.28​

Starting from version 1.28, the following updated method will replace both of the older methods:

<%@ Register TagPrefix="PaaTokens" Namespace="PlantAnApp.Dnn.Tokens.Controls" Assembly="PlantAnApp.Dnn" %>
<PaaTokens:Apply runat="server">
  Hi [User:FirstName]
</PaaTokens:Apply>

This change is available in version 1.27.418 and higher. At your option you can convert your pages to this method before upgrade to 1.28.

How to Prepare for Version 1.28​

  1. Identify Affected Themes:

    • Review your themes and locate any use of the current token methods as outlined above. This will help you identify parts of your themes that need updating.

  2. Complete the Updates:

    • Do it in advance (recommended)
      • Complete the theme update early - it will work starting at version 1.27.418 or higher.
      • Plan to test each impacted theme after the 1.28 upgrade.
    • Do it during the 1.28 upgrade
      • Prepare to update the themes with the new method immediately after upgrading to version 1.28.

Key Considerations​

  • Theme Errors: Following the upgrade, themes that haven’t been updated will display errors for pages using the older methods.
  • Ease of Transition: The change from the old to the new method should be straightforward for administrators and developers familiar with modifying themes.

Conclusion​

The move to a single, consistent method of token integration in themes aligns with Plant an App's broader goals of system-wide consistency and enhanced performance. Preparing for this change will ensure a seamless transition with minimal disruptions to your applications.

Revised 09/16/2025 (10055)