Skip to main content

DotNetNuke Upcoming Events setup of Calendar of Events

After much trial and error, spending endless hours on figuring out upcoming module with errors and issues I decided to find a better solution and what’s better solution than a xml and XSL.

I have been using “OTBMedia-UpcomingEvents” since 4.x, but it’s giving lot of issues in 5.0 so the need to find a better solution.

After initial start I realize the sort does not work with XSL as is but going over settings I see that I can manipulate the RSS output of the events RSS in “Template Settings” under settings.

Events >> Settings

[NOTALLDAYEVENT][event:startdate|g][/NOTALLDAYEVENT][ALLDAYEVENT][event:alldayeventtext][/ALLDAYEVENT] - [event:title]

After this manipulation I can easily format the xml in DotNetNuke’s XML/XSL module based on title, as the XML/XSL does not handles date correctly or at least to my knowledge.

XML >> XSL (code)

<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="
http://www.w3.org/1999/XSL/Transform">
<xsl:output method="html" indent="yes"/>
<xsl:param name="TITLE"/>
<style type="text/css">
.xmlEventLink{}
.xmlEventLink a:link, a:active, a:visited{}
.xmlEventLink a:hover, a:visited:hover{}
</style>
<xsl:template match="rss">
  <!-- Do not show channel image -->
  <xsl:for-each select="channel/item">
      <xsl:sort select="title"/>
    <br/>
    <!-- to open links in a new window, change target="_main" to target="_new" -->
    <div class="xmlEventLink"><strong><xsl:value-of select="substring(title,1,19)"/> - <a href="{link}" target="_main"><xsl:value-of select="substring(title,23,50)"/></a></strong></div><br/>
  </xsl:for-each>
</xsl:template>

<xsl:template match="description">
  <br/>
    <xsl:value-of select="."/>
  <br/>
</xsl:template>
</xsl:stylesheet>

--------------------------------------------------

To credit the right person, the XML above was originally part of a article/example and was edited for that article/example by (“Lee Sykes DNN Creative Magazine http://www.dnncreative.com”)

--------------------------------------------------

This is not the perfect solution but this is a start to resolve the upcoming events issue with DotNetNuke versions. I will keep tweaking along and see how best I can manipulate to find the perfect solution.

When I get a working solution I will post it along on this blog and may be also on www.techscrip.com under DotNetNuke tips and tricks.

Thanks,
Wasay


Comments

Popular posts from this blog

Completed UiPath - RPA Developer Advance Training

After a month of training, with late nights and weekends I have completed the UiPath RPA Developer Advance Training. The Level 1 Foundation Training pretty much covered all the basics of Desktop studio and workflows, only draw back was I started with the default foundation course which was for 2016, and all document reference links where pointing to 2016 version. I didn't understand it during the foundation training and kept switching to 2018 version document/page. Only after completing the Foundation course that I realized, I was suppose to have started with the 2018 version of Level 1 Foundation Training, but as it was optional I didn't have to retake the 2018 version, the 2016 was good enough for moving to level 2. The Level 2 Orchestrator 2018.3 Training as good. It gave good understanding of Queue's, Jobs, and schedules and I was able to complete the level two much faster then the level 1. The Level 3 UiPath Advanced Training was bit tough as it involved the a

KB 294807 - IIS Server - PHP FastCGI 500 Error 0xfffffffe

Resolved issue today of IIS Server - PHP FastCGI 500 Error 0xfffffffe by deleting "Windows Temp" folder files. We used Cygwin to customize some permissions of "Windows Temp" folder and after few hours the website stopped working. The search online was giving all kinds of different solution except what I was looking for. I was hoping the stackoverflow will have answers but even this post didn't cover the issue I was running into. https://stackoverflow.com/questions/15302080/fastcgi-500-failure Restarting the IIS didn't work, but deleting temp files cleared the issue, but now the problem is how long before the site will go down again? Hope the issue is resolved for ever, if not; I will update this post later.

QlikSense - Custom Form Login Screen

Extension of:  Custom login, logout and error forms for Qlik Sense by RPK https://developer.qlik.com/garden/5ada5a8f0c313f5c539dc7fd QlikSense - Custom Login Screen Install Node on QlikSense Server: URL: https://nodejs.org/en/ Saved at: C:\server-tools\Downloads\Node Installed at: C:\server-tools\Runtime\nodejs\ Keep default options Create Folder: C:\QlikForm Clone git Repository and keep updates private: # Open Shell/Bash/Command Prompt cd /QlikForm # Ref: https://medium.com/@bilalbayasut/github-how-to-make-a-fork-of-public-repository-private-6ee8cacaf9d3 git clone --bare https://github.com/kreta99/QS-Custom-Forms .git cd QS-Custom-Forms.git git push --mirror https://github.com/<name>/QS-Custom-Forms.git cd .. (go to parent folder) # remove other users repo clone rm -rf QS-Custom-Forms.git # clone witinc private repo git clone https://github.com/<name>/QS-Custom-Forms.git Get latest copy of login pages: # Open She