Bug with repeating event on the same day

[bcitweb]

We have a two day event that has multiple “tours” occurring on the same day. We want to model these as a recurring event in order to capture them as a series (events/recurring-event/all) but with custom setting for the time differences. That works as advertised.

The issue we are seeing is with the links to specific events on the events/recurring-event/all. They all link to the same post, the first one in the list:

[bcitweb]

All repeating events link to a url like events/recurring-event/yyyy-mm-dd/ and only the first event for the recurring event shows, regardless of what link we follow in the events/recurring-event/all list.

Maybe the name of this thread should have been a question, “Do single-day repeating events work?”

[George]

Hey James,

There is unfortunately no support for events recurring on the same day at this time. 🙁 Bugs like you describe will arise if you try to implement these sorts of events on your site.

We are working on better support for this, but at this time things are as I described here.

I’m sorry James!

Sincerely,
George

[bcitweb]

That’s a real shame, and a key aspect of what we’re using this plugin for, with regard to this specific event. Perhaps, since it doesn’t support multiple recurrences on the same day of a single entry, safeguards could be placed in the admin UI so that it doesn’t accept the parameters to create them, in the first place. In other words, once I’ve specified a start and end time on a given day, adding new times on the same day should be prohibited.

I guess the best we can do is create a single all-day entry for each day and then include all times in the description, or create multiple unique entries. The only problem with the latter approach is that it makes using the recurring events list feature incomplete, since users looking at that won’t see all occurences.

[George]

Hey James,

I agree that we could do a better job of communicating this lack of support—we are working hard on implementing these features, as well, so stay tuned to plugin updates over the coming months!

As for the entry solution you mention, I agree that this is tricky and not ideal and am sorry about the situation here. I wish you the best of luck with your site in the meantime.

If you have any other questions please let me know.

Sincerely,
George

[bcitweb]

Thanks Greg, but I think your response misses my point to some degree. It’s not just a lack of communication or a missing feature. If I can enter the data in the admin and it DISPLAYS CORRECTLY on the front end, showing all the recurrences on the SAME DAY, but only opens the first instance no matter which of the recurrences are selected, IT’S A BUG.

If it was just a missing feature, then it wouldn’t be able to do it at all. It’s a bug when the data displayed doesn’t reflect how it’s actually working.

[George]

Hey James,

I agree with you, and said this was a bug in my reply before last. Here’s a screenshot of that reply which is a few replies ago:

No snark here, James—I just want to make it clear that we are on the same page. This is a bug. We’re working on patching up this aspect of the edit-event process (and simultaneously the actual recurrence engine itself).

I’m sorry about this and appreciate your patience with us while we work on updates.

Let me know if you have any further thoughts on this matter or questions I can address.

Thanks,
George

[bcitweb]

Thanks George, apologies for missing it. It’s just too bad that the admin UI allows entry of the data and that the list views display it correctly, as it’s easy to miss if you’re not looking carefully at the single view. Could be kind of disastrous for end users on a busy event.

We’ll just either have to list all same-day occurrences in the description for one entry for the day or do each occurrence as a separate entry. Unfortunately, with this event a month away, the ‘coming months’ won’t help this time 😉

Just by way of general feedback, I’d suggest that charging $80 for the pro module when this functionality is borked for our use, is a little disappointing.

[George]

Thank you for your feedback, James. I’m sorry for the trouble here—keep your eye on plugin updates for the eventual improvements here.

Thank you,
George

[Author]

Posts