Closed rodkvan closed 1 month ago
Hello, @rodkvan ! Thank you for reporting this issue!
After some initial tests, we were unable to reproduce this, as yet, with a few different scenarios. This is the general procedure used:
Please let us know if this is not the same process, and how we can revise it to attempt reproducing the issue.
Could you also provide us with more details of a sample of the event configuration so we can isolate what might be causing the issue you are seeing?
And/or if you are willing to allow us to take a closer look at your account configurations, feel free to create a support ticket at:
https://dakboard.freshdesk.com/support/tickets/new
When opening the ticket, the following details would be helpful to have:
Thank you! --DanP
@Dan-Peck I have sent an initial email.
@Dan-Peck I have sent an initial email.
Okay, thank you @rodkvan ! We will attempt to analyze further. At a glance, one thing that could be useful is if you could also send along is either the full .ical
/ .ics
file, or specifically the section(s) of it that define the event having the issue. To do that, if you open the file or the URL content, and search for its title, it would look something like:
SUMMARY:The Event Title Here
Then, look up a bit farther, and the first line prior to the SUMMARY
line that reads BEGIN:VEVENT
... that is where its section starts. Grab that line, all the way down to the next END:VEVENT
. There is usually anywhere from a few lines to about 25 lines worth of content for a given event. Textual info can be redacted, but we will need the other lines like DTSTART
, RRULE
, SEQUENCE
, etc. to remain intact with its date/time and other frequency information. I suspect this may be related to an earlier reported, but inconclusive, Issue #2150.
As an example, a simple event entry would look something like this (there will be additional lines for your case):
BEGIN:VEVENT
SUMMARY:Thanksgiving Day
DTSTART;VALUE=DATE:20241128
DTEND;VALUE=DATE:20241128
LOCATION:United States
DESCRIPTION:Thanksgiving Day in 2024
UID:12345678901234567890abcdefg
DTSTAMP:20231015T092106Z
STATUS:CONFIRMED
TRANSP:TRANSPARENT
SEQUENCE:0
END:VEVENT
Note: It is possible there are a couple occurrences of the VEVENT
sections for the event, so you may need to repeat the above process for those.
Apologies for the inconvenience this has caused, but we do appreciate the additional details so we can address this!
Thank you! --DanP
@Dan-Peck - Thanks! I replied via the ticket with additional information.
Hi, @rodkvan ! -- We received the extra information, thank you very much! That was enough to do further analysis and reproduce the issue. This will now go into the work queue to be corrected.
Appreciate the report and the help! --DanP
@Dan-Peck - Amazing! Please advie when corrected and I will test on my end as well to validate.
Merged in @ af07a99 and added to the queue for upcoming release to the live site.
Hi Team,
Unfortunately we found this case's updates to cause some issues with the use of the EXDATE usage in apple calendars. This update has been reverted for now and the code changes will be re-evauluated.
Fixed revision merged in @ ae7d089 and added to the queue for upcoming release to the live site.
@Dan-Peck - Appears to still be an issue, have emailed the details.
@Dan-Peck - Appears to still be an issue, have emailed the details.
Thank you, @rodkvan ! Apologies for missing this scenario in the previous fix. I have added another adjustment to account for the discrepancy, as part of a new tracking case, #2246 and it is looking better. We will complete more thorough testing and have it released as soon as possible.
Describe the bug Cancelled event with ateendees still diplaying on DAKboard from iCal calendar feed.
Expected behavior Cancelled events should not show anymore.
Desktop (please complete the following information):
Additional context Same iCal link etc, load into Outlook or other mail client, cancelled events are removed almost immediately. So it is only showing on DAKboard. Happy to participate any any troubleshooting.