1. We have created components that use a .Net control to do the transformation. Appearance XML from the component. <ctz:Regionalization runat="server" XslPath="iwov-resources/xsl/product/region/productCrossSell.xsl" XmlPath1="ProductDetails||$MODEL{/Properties/Data/Datum[@Name='ProductDetails']/text()}" XmlPath2="Disclosure||$MODEL{/Properties/Data/Datum[@Name='Disclosure']/text()}" Datum1="ExistingURL||$MODEL{/Properties/Data/Datum[@Name='ExitingURL']}" ID="comp_$CONTEXT{componentId}" />
2. dotnet control in the component takes DCR path and path of XSL file as parameters. It does the transformation using dotnet APIs.
3. Issue is with page tokens. Where there is requirements to get the link of a page dynamically, we are using PAGE_LINK token. Few links we are passing as 'Datum's to the control and it just works fine. Few DCRs are having $PAGE_LINK tokens within. Content authors enter links to the "Description" field of DCR using TinyMCE. Authors are using $PAGE_LINK token to specify the URL for the links. These $PAGE_LINK tokens are not getting substituted with actual links. Please refer attached screenshot for the HTML rendered. Need your help to understand how to get the PAGE tokens from DCRs to display correct content when we are working with IIS runtime and .Net controls. Additional information: TeamSite & LiveSite 7.4.1 Runtime - dotnet Component type - HTML. dotnet control embedded in Appearance XML. Please let me know if you need any additional information.
