recurring events on front page

[lancerasmussen]

I would like recurring events to show on my front page, but only the first of each recurring event that is current.
I have the cleanup set to the minimum of 1 month.
I have a couple recurring weekly events and I want to make sure it is shown for the current week, not the past.
I.E. I have 2 events that showed Jan 20th and since that day has past, I want the next occurrence of Jan 27th to show. The only way I can see that I can do this is to show all recurrences, which then doesn’t work because the front page is based on newest to oldest, so a viewer won’t see that an event is coming up shortly.

[Barry]

Hi @lancerasmussen,

So just to clarify you have integrated events into your main blog loop and it is there that you wish this change to take effect?

[lancerasmussen]

Correct. I had to change the event Start date to be today in order to show todays events and not last weeks events.

[Barry]

OK: a snippet like this one could be added to your theme’s functions.php file – it should cause only the first upcoming recurring event to be exposed within the main blog loop. Hopefully that gives you at least a starting point for your own solution 🙂

[lancerasmussen]

Thank you. While I applied the code to the functions.php and unchecked “Show only the first instance of each recurring event), your solution does not appear to be working.
While only one of each recurring event is displaying, it does not appear that it is honoring the date of the event, so that it is not the first upcoming event.
http://www.westseattlearc.org If you look at the last two events in the main blog loop, you will see two weekly nets, yet the dates are for yesterday. Since that date has passed, it should take the next weekly dates for those events, which is Feb 3rd.

[Barry]

Yep, I think unfortunately you are hitting a different bug. Actually if you follow one of those links you will find you are indeed brought to the next upcoming event in the series (not the one that has passed).

Recurrence is undergoing some large scale refactoring right now and I would be hopeful of this being resolved after that point, until then I’m not sure there is too much more we can do, regrettably.

[lancerasmussen]

I hope it can get resolved soon. Recurring Events is why I purchased the Events / Events Pro module. It is important to “roll off” the occurrences one they are past.

It’s important to have, in terms of days, the time for an event and event occurrence to roll off. Example, I may want to show an event that has passed two weeks ago. But for a weekly occurrence, I want it to roll off the next day.

I also noticed that if I delete a recurring event that has past, that event with all the recurrences will be deleted. My suggestion in the admin is to have a “Master” occurrence and then display the recurrences underneath. If you delete a recurrence, no problem. If you need to make a major change, you edit the “Master” occurrence.

[Barry]

It’s important to have, in terms of days, the time for an event and event occurrence to roll off. Example, I may want to show an event that has passed two weeks ago. But for a weekly occurrence, I want it to roll off the next day.

OK – however this sort of thing is likely to remain the preserve of customizations, as not everyone would find that desirable. Though what I would recommend is putting your thoughts together and posting this as a feature request on UserVoice – that way others can endorse or otherwise comment on the idea (and we’d gain a better sense of whether or not it had enough traction to warrant a change to core plugin code).

I also noticed that if I delete a recurring event that has past, that event with all the recurrences will be deleted. My suggestion in the admin is to have a “Master” occurrence and then display the recurrences underneath. If you delete a recurrence, no problem. If you need to make a major change, you edit the “Master” occurrence.

You should be able to edit past recurring events and – so long as you are within the actual editor and not the list – trash that instance and that instance alone. Intereestingly, your concept of a master event with individual instances that are subordinate to it is very close to what is being developed during the refactoring process – so it certainly seems like we are indeed headed in a direction you’ll be pleased with.

Right now though there isn’t too much more we can offer: please do monitor the forum and blog for updates and if you would like to make one or more feature requests relating to this they would be very welcome 🙂

Thanks!

[Author]

Posts