0
Undo
Votes
Quite often if not in nearly every single case, an annual event that repeats on a specific month/day will appear on the wrong day, typically a day late. Case in point is 'Cinco de Mayo', which occurs on May 5 annually. This year and most prior years, it has appeared on the calendar on May 6. You can see this at this URL. This has actually been a problem for quite some time, predating Joomla 4. I've always just assumed it had something to do with time zones, but that would change its behavior based on the current time of day and it doesn't.
bascherz
set the post as Normal priority — 1 year ago
I notice that the problem doesn't arise in Leap Years - I'm guessing you may have created this as a day count annual event during a leap year and when its not a leap year the lack of Feb 29th moves the event forward one year.
You should either
1. Make this a monthly event on May 5th repeating every 12 months, or
2. Count backwards from the end of the year
You should either
1. Make this a monthly event on May 5th repeating every 12 months, or
2. Count backwards from the end of the year
JEvents Club members can get priority forum support at the Support Forum. As well as access to a variety of custom JEvents addons and benefits. Join the JEvents club today!
I think you may be right. I entered that event in 2020 as an annual event, and it was correctly on the 5th of every leap year. So I edited the main event and changed the start date to 5/5/2021. That fixed all the ones NOT on leap years and the ones in leap years switched to the previous day (4th). So it seems JEvents needs to be smarter about how it deals with leap years.
You should either
1. Make this a monthly event on May 5th repeating every 12 months, or
2. Count backwards from the end of the year
See https://www.jevents.net/docs/jevents/item/repeat-event-annual-event
JEvents Club members can get priority forum support at the Support Forum. As well as access to a variety of custom JEvents addons and benefits. Join the JEvents club today!
- Page :
- 1
There are no replies made for this post yet.