Forum Replies Created
-
Posts
-
I could definitely do that, but I have events as recent as a month or two old that are still affected by the same bug, so I’m not convinced the age of the events has much to do with it. And unless I’m sure that’s a solution, it’s actually quite a lot of work to do, given the volume of weekly events I have.
Hey Jaime! Those exclusions are actually automated by the Events Calendar. I have it set to show past events for two years, and apparently the Event Calendar’s solution to that is to start generating “custom” exclusions for instances of the event that are more than two years old, which it also only seems to do when I update the event. I have lots of weekly events, many of which are as old as this one, and many of which are relatively new. Unfortunately, this problem affects all of them, so it can’t just be a matter of my event being too old. I realize it’s a difficult problem to replicate because it involves at least a day to see what the calendar does each day, but it seems like it’s a bug (or bizarre feature) in the coding for the way the calendar knows how to show or hide events with no expiration.
I’m not sure I have the time or energy to go through all that. I will say that this issue seems to happen most often if I update a recurring event before a different recurring event has finished updating. It pretty routinely seems to result in the former showing up on the front-end as an 8:00am event (but everything looks right for the appropriate time on the back-end). Not sure if that helps isolate a cause.
I’ve seen it requested as feature before (as here: https://tribe.uservoice.com/forums/195723-feature-ideas/suggestions/18784744-for-event-tickets-make-rsvp-default-to-1-instead), but it always gets declined, even though there are ways to implement it that wouldn’t break people’s sites. The response to the feature request I linked mentions a solution under development. I presume as an extension? Anywhere I can sign up for info on that when it’s done? Or is it done already, by any chance?
Here are two shots of our calendar, a before and after. All I did between these two pictures was hit “Edit All”, take some screen shots, and hit “Update”. In the before, you’ll see that LCG Night has decided not to show up beginning August 1st. In the after, it’s on there for August 1st (and showing up through October 10th).
Thanks!
Hey Josh–
I appreciate the response. I guess I’m just not sure why that intended functionality would ever be preferable. “Edit Upcoming” seems like a useful feature only in so far as it allows you to change the way an event works going forward from a certain date. I know what it’s actually doing behind the scenes, but in practice what it’s useful for doing is changing one or more details about my recurring event beginning with whatever upcoming date I specify. I can’t think of a single example of an ongoing event (set to end “Never”) that would benefit from the original listing mysteriously re-appearing on the calendar after a more-or-less arbitrary number of months. Even if such an event exists, it would seem to be significantly less common than the alternative, and could be just as easily implemented as the current workaround for this issue.
