Working with dnn 4.4.1 xml/xsl v04.03.03 on a local install using xp pro sp2.
The previous version of the XML/XSL module had no trouble when I was using a custom xml / xsl combo that uses scripts inside the xsl. The header is like this:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:msxsl="urn:schemas-microsoft-com:xslt"
xmlns:user="urn:my-scripts">
The script is a simple implementation of a call to a user function:
<msxsl:script language="C#" implements-prefix="user">
<![CDATA[
public string today(){
return (DateTime.Now.ToString("yyyyMMdd"));
}
public string TodayDateTime(){
return (DateTime.Now.ToString("yyyyMMddHHmm"));
}
]]>
</msxsl:script>
After upgrading to the new version, I'm getting the following error:
System.Xml.Xsl.XslTransformException
Execution of scripts was prohibited. Use the XsltSettings.EnableScript property to enable it. An error occurred at C:\dnn4x\WebSite\Portals\0\iLinksNew.xsl(94,1).
The offending xsl line is where the script is invoked.
<xsl:variable name="myCurDate" select="user:today()"/>
The module was working before the upgrade to the new version with the same xml source and xsl transformation file.
In the error message a references is made to 'Use the XsltSettings.EnableScript property to enable it.' Where exactly is this property enabled?
Any reason why this feature is not supported in the new version, but is in the previous version?