Every event listing twice

I’ll be a little more clear. I use the plugin to list open hours. Each event title is simply the opening hours i.e. 7:30am to 10:pm. So I have a list that simply displays the date and the title – it appears that with the update it now lists the date and title followed immediately by the date and a time? As it is not the title but I’m not sure where it could possibly be getting this time from. So this is what I end up with:

Monday, 23rd Jun
7:30am – 9:00pm
Monday, 23rd Jun
7:30am – 12:00am
Tuesday, 24th Jun
7:30am – 9:00pm
Tuesday, 24th Jun
7:30am – 12:00am
Wednesday, 25th Jun
7:30am – 12:00am
Wednesday, 25th Jun
7:30am – 9:00pm

Reverting to 4.6 fixes the issue – so something definitely wrong/new with the update.

hmm maybe… – was supposed to affect RDATEs only.
NO just checked that – does apply to rdates only… checking further

Hi cannot recreate problem – all seems fine at https://test.icalevents.com

Are you using RDATES to create your opening hours somehow?
You may have been using a ‘bug’ where the DTSTART was not properly included when there were RDATES. See
https://icalevents.com/forums/topic/recurring-date-first-date-not-in-list-view/

Can you post the public url of the ics file and I’ll see if I can recreate it.

Thanks for the quick response – here is the public URL:
https://www.google.com/calendar/ical/aus.library%40gmail.com/public/basic.ics

Yes I think we have a ton of never ending recurring events that could be causing the issue. I’m going to attempt truncating those recurrences and see what happens.

That urk gives

Feed Processing Error

what is the url you have put into the shortcode?

Well that is disconcerting – here is the private URL from the shortcode:

https://www.google.com/calendar/ical/aus.library%40gmail.com/private-112a221dc0921d6bc022bb21d03e8773/basic.ics

Hi,
1) all urls to be fetched must be ‘public’ – even if it is a public url for a private calendar

2) I hate to say it It looks like maybe you have totally confused google – this is what it looks like. I cannot recreate it, but your calendar does have a LOT of event mods – maybe it hit some kind of limit.

For example: You have 57 instances of a UID (Unique Idntifier for a event recurrence)
[email protected]’
which means you have 57 modifications to instances of the event set.
Now the individual recurrences have SEQUENCE:2, BUT SO DOES the RRULE.

NOW a event key is defined as
UID plus RECURRRENCE ID plus SEQUENCE.

The highest sequence wins – ie: it is deemed to be the latest.

Now in this file, The original event set is at line 6318 and already has SEQUENCE:2. (they start at 0 says RFC 5545 https://tools.ietf.org/html/rfc5545#section-3.8.7.4). So the set itself had at least 2 mods.

BUT the recurrence mods ALSO have sequence 2. The RECURRENCE-ID’s define the instance they are modifying an dthe rest of the data defines the ‘new’ data that is replacing rte default of the recurring data. They should have a HIGHER SEQUENCE No. Else how does one define via logic which is the latest and therefore valid modification?

According to the spec, the situation on your file should not happen (and I canot recreate it). So while one could say maybe the plugin should assume a RECURRENCE_ID .

Interestingly if one “imports” that file into a new test google calendar, then google ignores the possibly invalid ‘mods’ that have the same sequence number (i think)
See this image of re-imported events
https://i.imgur.com/xOOJjNA.png
vs this image where the plugin is listing both, the recurrence-id date and the sequence number.

https://i.imgur.com/OFsK0BD.png
Note: Google reported 430 events imported!

I’ve googled a bit and cannot see whether what google does on re-import is right or not. Basically as I understand it the situation should NOT occur.

So I’d say your best bet is to cleanup. Perhaps start a clean calendar with a clean set of “opening hours” it will also improve the parsing.

https://tools.ietf.org/html/rfc5545#section-3.8.4.4 Recurrence-id

In your file:
Original event set: (around line 6318)
BEGIN:VEVENT
DTSTART;VALUE=DATE:20121010
DTEND;VALUE=DATE:20121011
RRULE:FREQ=WEEKLY;BYDAY=WE
EXDATE;VALUE=DATE:20121031
DTSTAMP:20140625T101245Z
UID:[email protected]’
CREATED:20121118T044458Z
DESCRIPTION:
LAST-MODIFIED:20121118T071534Z
LOCATION:
SEQUENCE:2
STATUS:CONFIRMED
SUMMARY:7:30am – 12:00am
TRANSP:OPAQUE
END:VEVENT

One of the modified recurrence instances – much earlier in file)
BEGIN:VEVENT
DTSTART;VALUE=DATE:20140903
DTEND;VALUE=DATE:20140904
DTSTAMP:20140625T101245Z
UID:[email protected]’
RECURRENCE-ID;VALUE=DATE:20140903
CREATED:20121118T044458Z
DESCRIPTION:
LAST-MODIFIED:20140602T095116Z
LOCATION:
SEQUENCE:2
STATUS:CONFIRMED
SUMMARY:9:00am – 5:00pm
TRANSP:OPAQUE
END:VEVENT

I tried to replicate this in google. But could not. In the example below you see the main event is sequence 1 and the modification to the recurrence is sequence 2. I then made a change to all – it set the main recurring rule to sequence 2. I then changed a single instance again and it set that to sequence 3. Basically I was unable to recreate in google calendar what is in your file.

BEGIN:VEVENT
DTSTART;TZID=Australia/Sydney:20140730T230000
DTEND;TZID=Australia/Sydney:20140731T000000
DTSTAMP:20140625T111840Z
UID:[email protected]
RECURRENCE-ID;TZID=Australia/Sydney:20140730T220000
CREATED:20140625T111750Z
DESCRIPTION:
LAST-MODIFIED:20140625T111822Z
LOCATION:
SEQUENCE:2
STATUS:CONFIRMED
SUMMARY:Test Recurrence
TRANSP:OPAQUE
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=Australia/Sydney:20140723T220000
DTEND;TZID=Australia/Sydney:20140723T230000
RRULE:FREQ=WEEKLY;BYDAY=WE
DTSTAMP:20140625T111840Z
UID:[email protected]
CREATED:20140625T111750Z
DESCRIPTION:
LAST-MODIFIED:20140625T111806Z
LOCATION:
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:Test Recurrence
TRANSP:OPAQUE
END:VEVENT

Thanks for looking into this so extensively. It has me mystified but I created a fresh calendar and made some adjustments to how I create the recurring events. I am also using the public URL as you point out.

In the end a fresh start to the calendar fixes my issue – update to 4.7 works without issue now.

Thanks again
James

This problem has suddenly returned despite the new calendar. Its incredibly strange as the first few dates appear fine and then suddenly they begin duplicating though it appears it is not spitting out the name of the event but something different. Have a look at this screenshot (notice the times – event names – are different):

https://www.dropbox.com/s/9f387utz4v3objq/Screenshot%202014-07-02%2007.26.21.png

You’ll see the “duplication” begins on the 6th. Fridays do not appear to be subject to the problem, oddly enough. I assumed it was a recurrence issue so attempted to make the first two weeks individual daily events (cleared cache, forced a reload of the calendar by adding a query to the url) nothing. What makes it even more odd is that a roll back to 4.6 no longer seems to solve the problem.

here is the public URL: https://www.google.com/calendar/ical/h6d60atl1al814ddghf1l9aog4%40group.calendar.google.com/public/basic.ics

I can successfully load this calendar into Apple Calendar without a problem. Any ideas would be appreciated.

Thanks

I think the plugin is not calculating recurring event start dates properly. It appears the recurring events are beginning the week previous to their start date. See this screenshot:

https://www.dropbox.com/s/vx38g4bdqv4ogvz/Screenshot%202014-07-02%2010.03.52.png

Hi JRW
In your last screenshot the two vevents are shown correctly (note they are not recurring events – just simple flat events and are shown on the date of the DTStart.

So it is not clear what you are expecting ?
Try comparing to agenda style displays in other calendar apps or even in google itself

Sorry that screenshot was messed – I meant to show the following event:

BEGIN:VEVENT
DTSTART;VALUE=DATE:20140713
DTEND;VALUE=DATE:20140714
RRULE:FREQ=WEEKLY;UNTIL=20140721;BYDAY=SU,MO,TU,WE,SA
DTSTAMP:20140703T035432Z
UID:[email protected]
CREATED:20140626T044437Z
DESCRIPTION:
LAST-MODIFIED:20140626T044706Z
LOCATION:
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:7:30am – 11:00pm
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR

You can see that this recurring event (the only one in the file with the label/summary of 7:30 – 11:00pm) should begin on July 13th and run until July 21st. However, the event shows up starting the week previous on July 6th.

This is the case with all recurring events – they begin a week earlier than the start date indicates (which accounts for the duplication – its not duplication just that there are now two events scheduled for the same day).

Any recurring event begins a week earlier than the start date indicates.

Hi just to let you know I’m looking at it.

Weirdly all is fine with events created with amr-events with BYDAY recurrences, eg:
https://test.icalevents.com/event/opening-hours/

however when event comes from google AND has BYDAY recurrence it seems to start a day earlier (not a week)
at first I thought maybe a timezone issue.

It’s a bit hard to debug easily here (on island) so it may be a few days till i see what is going on – seems to be a BYDAY thing.

will update whne i have more info

I appreciate you looking into it – and the update.

Cheers
James