iCAL SubCalendar Name Missing

[PeterCasper]

G'day All,

we have about 20 regular event organisers. Each has been given their own sub-calendar with moderated access to manually resolve any scheduling clashes. When the combined calendar is exported using iCAL the events get titles such as:

SUMMARY:Regular Meeting

rather than the extended event title seen on the combined calendar featuring the sub-calendar name in brackets.

Can I correct this with a template change?

Thank You Peter

[PeterCasper]

I so wish I knew how to code. I am confident the problem is in iCalProvider.vb at lines 578 & 723.

The first references oEventRecurMaster.EventName & the latter oEvent.EventName.

The "EventName" part is wrong because it only returns the EventName field.

It needs to be a calculated object; an object with the same definition as "[event:title]": Event title and the sub calendar modulename when defined in settings.

Unfortunately, further is currently beyond my skill level. Can anyone please help fix this?

Thank You Peter

[PeterCasper]

Am I the only one using iCAL & SubCalendars? Should I be looking at alternate calendar management?

[PeterCasper]

Is this still in the "too hard" basket?

[EPTamminga]

It is still on the list to do. The conversion to C# had more (negative) side effects than expected. And since I am on holiday till end of nov, do not expect any change on this very soon. Sorry.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[PeterCasper]

WAAAHHHH!!!!!!!!

From: stale[bot] notifications@github.com Sent: Tuesday, 4 February 2020 6:26 PM To: DNNCommunity/DNN.Events DNN.Events@noreply.github.com Cc: Peter Casper Peter@casper.com.au; Author author@noreply.github.com Subject: Re: [DNNCommunity/DNN.Events] iCAL SubCalendar Name Missing (#45)

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/DNNCommunity/DNN.Events/issues/45?email_source=notifications&email_token=AGBFMQV75OIDAECMU6TRSPLRBERDFA5CNFSM4C5QG3K2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKWX3GI#issuecomment-581795225, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGBFMQX4OWX2347NUJA4NX3RBERDFANCNFSM4C5QG3KQ.

[EPTamminga]

I understand your "WAAAHHH".... I am just trying to do some cleanup of issues...

[FrancSimari]

You are also cleaning up all suggestions, have the suggestions been evaluated?

Franc Simari

https://momzey.com/ Momzey.com

978 375-7275

From: Ernst Peter Tamminga notifications@github.com Sent: Tuesday, February 04, 2020 6:07 AM To: DNNCommunity/DNN.Events DNN.Events@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: Re: [DNNCommunity/DNN.Events] iCAL SubCalendar Name Missing (#45)

I understaand your "WAAAHHH".... I am just trying to do some cleanup of issues...

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/DNNCommunity/DNN.Events/issues/45?email_source=notifications&email_token=AC3WHCXJCA22EODXRDZLWHDRBFD3VA5CNFSM4C5QG3K2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKXG4UA#issuecomment-581856848 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AC3WHCX4LYNPOTXQZZR3YQTRBFD3VANCNFSM4C5QG3KQ . https://github.com/notifications/beacon/AC3WHCTGWZ2APRIZTYUTMCDRBFD3VA5CNFSM4C5QG3K2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKXG4UA.gif

[EPTamminga]

@FrancSimari

Suggestions for enhancements have been inspected, but.... if there is no activity for 6 months (an arbitrary period I just set for the bot) and nobody is addressing the issue or create a PR, the suggestion might still be valid, but it will clutter the list of issues. It might well be that the issue is made by a person who moved away from the module to another solution and that the issue is no longer relevant.

Please note that the issue is not gone, it will just be marked as "closed" after 21 days after marked as stale.

If somebody enters a comment in the issue in a period of 21 days, while the issue is marked as "stale", it will start a new period of 180 days.

The stale bot principle is copied from DNNPlatform, although the DNNPlatform uses shorter periods to keep the list of DNNPlatform issues clean and actual.

[PeterCasper]

I now have 23 sub-calendars with a 24th requested last week-end.

On the main calendar, the events are all easily recognizable with generic event names but unique identifiers from each sub menu (named after the organizing group) in brackets. The iCAL only shows the generic event names. The event organisers would like to distribute their calendars & the combined calendar however they can currently only do it via screen dumps.

[EPTamminga]

@PeterCasper I know you have made this request a long time ago. I did spend quite some time trying to include this in the iCal some time ago, but the code was not made by me, quite old and not very clear. So, until now, no success with this request sofar. Sorry. The request is still valid.

[stale[bot]]

We have detected this issue has not had any activity during the last 180 days. That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue. We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 21 days, the issue will be closed automatically. If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future. Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all. Thank you for your continued involvement and contributions!

[PeterCasper]

Bump?

[stale[bot]]

We have detected this issue has not had any activity during the last 180 days. That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue. We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 21 days, the issue will be closed automatically. If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future. Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all. Thank you for your continued involvement and contributions!

[PeterCasper]

I still have members requesting this.

[stale[bot]]

We have detected this issue has not had any activity during the last 180 days. That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue. We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 21 days, the issue will be closed automatically. If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future. Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all. Thank you for your continued involvement and contributions!

[PeterCasper]

Bump