offset and show_recurrent_events_once behavior

[bobbybosler]

Hello there Franky,

Question. I'm calling my events list in a bit of an unusual way (via the offset parameters) so that I can build them in my page builder, instead of from scratch with html. I'm calling the [events_list] shortcode with templates to dynamically populate my different events where I want them and then using offset to shift between first, second, and third events (and so on).

However, I'm finding that that the show_recurrent_events_once parameter isn't exactly surfacing what I want. Because each instance is technically a new [events_list], my recurring events are all showing up. I guess I was hoping the offset recurring event would be counted so that the remaining events wouldn't include the recurring event.

Boy, that's not very clear. Here are my events

Volunteer Work Day,

1. Ladies Bible Study,
2. Ladies Bible Study,
3. Volunteer Work Day,
4. Missions Conference,
5. Ladies Bible Study,
6. Ladies Bible Study,
7. Ladies Retreat,

You can tell which ones are recurring, right?

Here is what I'm calling:

[events_list offset=0 show_recurrent_events_once=1]
[events_list offset=1 show_recurrent_events_once=1]
[events_list offset=2 show_recurrent_events_once=1]
[events_list offset=3 show_recurrent_events_once=1]

Ideally, I'd like that to return:

1. Volunteer Work Day,
2. Ladies Bible Study,
3. Missions Conference,
4. Ladies Retreat

So here's what I'm wondering. I wouldn't want my fringe application to mess anyone else up. Can you introduce a show_recurrent_events_once=2 option that lets skipped-via-offset recurrent events be counter towards the "once"?

I hope that makes sense.

[liedekef]

untested, but do try this change:
9c38160

[liedekef]

this is now in production too btw

[bobbybosler]

I tested in production, but now it appears that the offset doesn't work now at all when show_recurrent_events_once=1

[liedekef]

weird ... anyway, I reverted that change and will take a look at it later in the future. You can download the corrected eme-events.php file:
https://raw.githubusercontent.com/liedekef/events-made-easy/refs/heads/main/eme-events.php

[bobbybosler]

So let me try at this again.

What I think the issue is, is that offset is not factoring in the show_recurrent_events_once=1.

So, if I had:

Item 1 (recurrence 1)
Item 2 (recurrence 1)
Item 3 (recurrence 1)
Item 4
Item 5
Item 6

If I did [eme_events limit=1 offset=0 show_recurrent_events_once=1], I currently get Item 1
If I did [eme_events limit=1 offset=1 show_recurrent_events_once=1], I currently get Item 2
If I did [eme_events limit=1 offset=2 show_recurrent_events_once=1], I currently get Item 3
If I did [eme_events limit=1 offset=3 show_recurrent_events_once=1], I currently get Item 4

But that's not what I was hoping for. I was hoping for the following
I was hoping that [eme_events limit=1 offset=1 show_recurrent_events_once=1] would get me Item 4, since the skipped item (offset=1) was a recurrent event and should have "triggered" already.

Does that make sense?

Currently, in my Upcoming Events section on fbcfairmont.com I am having to get very creative and use multiple [events limit=4 show_reccurent_events_once=1] with various templates and then do :nth-child display:none's to achieve the effect I desire. But it leaves some pretty messy code that this solution would clean up my html output significantly.

[liedekef]

The reason is that the offset is being done before the limit, and there the recurrent events are 'included'. This is because it is not an easy sql to write (because you want to make sure you have 1 recurrent event shown too, even if some of the series are not in scope of what you want to show).
I'll look over the sql again but can't promise anything right now

[liedekef]

ok, first update to the latest EME release and then download eme-events.php from github: https://github.com/liedekef/events-made-easy/blob/main/eme-events.php (and replace on your end). See if that gives an expected result (it does here: I learned about GROUP BY combined with CASE ...)

[bobbybosler]

Yes, it works! Wonderful! Any idea when that would come out in production?

[liedekef]

I first need to run more tests, since group by doesn't necessarily give you the first row ...

[liedekef]

as suspected, there was an unpredictable result (due to the GROUP BY). Now fixed, please get the latest eme_events.php code and try again

[bobbybosler]

I updated, no issues that I can tell.

[liedekef]

then keep using that new file until the next version releases.