I'm trying to display recurring calendar events (either Recurring Event asset or Multi-date asset) in the month view of a calendar asset, but can't get the display that I want. The events occur every Saturday of the month, but when listing the items out on the calendar page with either %instance_start_datetime% or %event_start_datetime% the event is only listed once.
Example:
That recurring dates are 3, 10, 17, 24, and 31 March.
%event_start_datetime% only displays for 3 March.
%instance_start_datetime% only displays for 3 March.
What I would like to have is an individual line for each instance of the recurring event listed out on the calendar page. Has anyone done this or have an idea how to achieve the desired results?
Additionally is there an option now or in the future to set an event to not display on a set date? i.e. event occurs on every Saturday, except the first Saturday of each month.
[quote]
I’m trying to display recurring calendar events (either Recurring Event asset or Multi-date asset) in the month view of a calendar asset, but can’t get the display that I want. The events occur every Saturday of the month, but when listing the items out on the calendar page with either %instance_start_datetime% or %event_start_datetime% the event is only listed once.
What I would like to have is an individual line for each instance of the recurring event listed out on the calendar page. Has anyone done this or have an idea how to achieve the desired results?
Additionally is there an option now or in the future to set an event to not display on a set date? i.e. event occurs on every Saturday, except the first Saturday of each month.
[/quote]
Hi,
You might find the answer in bug report #4929 Calendar Page - Recurring event not working when using “List without headings”.
Ash
Thanks Ash that bug report was spot on.
I've got another issue with the recurring events and didn't want to start a new thread.
Using keywords %asset_attribute_start_date% %asset_attribute_end_date% on a paint layout for a recurring event only ever shows the first events date/time - which makes sense as the manuals say that this will only show the first instance. However using the keywords %instance_start_datetime% and %instance_end_datetime% never displays at all.
E.g. Event occurs over three weeks on 3, 10, 17 June 2012. On each individual events page it will always display 3 June 2012 using the %asset_attribute_start_date% keyword, but I want to use the %instance_start_datetime% keyword.
Ideas?
=========
Woops, never mind its sorted. I was using %asset_name_linked% which wasn't adding ?SQ_CALENDAR_DATE=2012-06-16 to the url, so instead I just had to link using %asset_url%.
[quote]
I’ve got another issue with the recurring events and didn’t want to start a new thread.
Using keywords %asset_attribute_start_date% %asset_attribute_end_date% on a paint layout for a recurring event only ever shows the first events date/time - which makes sense as the manuals say that this will only show the first instance. However using the keywords %instance_start_datetime% and %instance_end_datetime% never displays at all.
E.g. Event occurs over three weeks on 3, 10, 17 June 2012. On each individual events page it will always display 3 June 2012 using the %asset_attribute_start_date% keyword, but I want to use the %instance_start_datetime% keyword.
Ideas?
[/quote]
Hi,
This issues seems to be bug #4899 Recurring calendar event instance date keyword bugs. Can you confirm if your system version is previous to the version the bug is fixed on. Also can you see any errors in the error log when you try to use the instance keywords?
There has actually been quite a few bug fixes recently in calendar package. I can give the issue go on my system to see if I can replicate it if you already have the above mentioned bug fix.
Ash
[quote]
Woops, never mind its sorted. I was using %asset_name_linked% which wasn't adding ?SQ_CALENDAR_DATE=2012-06-16 to the url, so instead I just had to link using %asset_url%.
[/quote]
Okie dokie 
We are running 4.6.1 and I didn't get any of the errors outlined in the bug files. Thanks for looking into this though.