I am having trouble using the iCAL icon to allow users of our website to subscribe to our calendar.  If the click the iCAL icon at the top of the calendar they can do a one time download and export/import our calendar, but that is not what they want.  They would like access to the URL that can be used by other calendars such and Google and Cozi to subscribe to our calender.  That will allow them to see changes to our calendar when they view their calendar.

I read the documentation and found:  "The module settings show the basic url that is used to generate the whole module .ics. You can also turn on the iCal icon on the icon bar for easy access to this url for your users. The url can be used within applications such as MS Outlook or Google Calendars to 'subscribe' these applications to your DNN based calendar. Please look at the documentation for those applications on how to set up subscriptions."  I do not want to give everyone access to the module settings so they can find the basic URL that is needed to subscribe to our calendar.  I have turned on the iCAL icon, but it only downloads.  Even if I right click this icon, the "Copy shortcut" option is grayed out (that is how I get the iCAL URL of calendars on other websites).

Is there any way to provide users the iCAL URL without giving them access to the event settings?

Thanks,
Greg

I've done better than that, I have added the fix to the 5.2.3 beta release available on CodePlex.

Bug posted here - http://dnnevents.codeplex.com/workite...

---

DNN MVP
Events - Get the latest version - Upgrade now!!
Feedback 6.4.2 - Now available - Give it a go!
Find us on Codeplex - DNN Events, DNN Feedback

---

Requirements/Bugs - Please submit them on Codeplex

Well the iCAL URL issue is fixed ... thanks!

Now I have a problem with events 5.2.3 where I cannot add or edit events after upgrading from events 5.2.0.  What happens once I click on add or edit for an event, I see the wait image (the circle rolling clockwise).  This remains indefinitely.  I am using DNN 6.0.1.

I believe my problem is similar to this:  http://www.dotnetnuke.com/Resources/F...
but that solution does not solve the issue for me.

I have found if I disable the popups for the portal, I no longer have the issue.  Should I be using events 6.0.0 instead?

Thanks,
Greg