Just wanted to add a bit to this discussion...
I was previously using an embedded script inside my xsl to accomplish this type of usage, but as Stephan pointed out, using embedded scripts incurs a heavy performance load, as well as opens up some security issues. So, support of xsl scripting was removed from the latest release.
So, I made the changes as previously mentioned, but with a slight difference which gives me the ability to use the module in the manner we need. The post title indicated that this would provide PortalDate info, but actually, the method illustrated is pulling the date info from the Server point of view. So, I made my mods as follows:
Case ParameterType.ServerDate ' Custom CurrentDate
Return Date.Now.ToString("yyyyMMdd")
Case ParameterType.ServerDateTime ' Custom CurrentDate
Return Date.Now.ToString("yyyyMMddHHmmss")
You can see I named the options ServerDate, and ServerDateTime. We did it in this manner to support using a custom xml file that contains button links that have a pubDate and ExpireDate. With these 2 options, we can use XML/XSL to dynamically display the button links for the desired period of time. It's an older method of providing user site navigation, but it was needed to support the client's need.
If the module is updated to include this kind of support for DateTime, it's important to implement it with the correct point of view, which means that support is needed to display the Server date time info, and the Portal date time info. At least, that's what I'm doing, and I would like to see it incorporated in future releases, just to save me from making the mods myself, but now that we have the knowledge to do it, it's not that big a deal, but would be appreciated.
Thanks for sharing the info...