In Hawaii, we do not adjust for DST. I created recurring events for 4p. After the DST adjustment, those events now show 5p. As a result, Scouts missed meetings. However the calendar is handling DST is broken for locations that do not adjust their clocks.
@DaveMorris - have you verified the timezone setting in scoutbook classic AND scoutbook plus is correct.
@DaveMorris - and you are seeing the issue on the scoutbook plus calendar but it is good on your pack g-cal ?
When the developers look at your events, they are displaying the correct time. Did you re-create the events after you noticed the time was off?
Another question from the developers. Were the events created directly in SB+ or with the Feature Assistant Extension for Scoutbook and Firefox?
In response to both of your questions:
-
Yes, I adjusted them all. This came to my attention because a 3rd grader and his mom were very upset when they showed up at 5p for a meeting that was scheduled from 4-5p.
-
I created these directly in SB+ using the recurring meeting function. It is my understanding that the extension is deprecated.
It is still available from my dashboard in legacy scoutbook.
1 Like
Two more questions from the developers:
- When did he originally create his den meeting series in SB +?
- For his recurring series for leadership committee meetings. Does the one on 7/21 reflect the proper time? Meaning did that adjust incorrectly with DST (that one should not have been adjusted by him and will allow me to compare apples to apples). When was that series created?
1. When did he originally create his den meeting series in SB +?
There are two Den Meeting series. One that first occurred on 9/1, which repeats on the first Sunday of every month. That was created sometime in August. The other first occurred on 10/20, and repeats on the 3rd Sunday of every month. That one was created in early October.
2. For his recurring series for leadership committee meetings. Does the one on 7/21 reflect the proper time? Meaning did that adjust incorrectly with DST (that one should not have been adjusted by him and will allow me to compare apples to apples). When was that series created?
The event on 7/21 shows the correct time, but it was created that month and should be a one-time (non-recurring) event.
As a test case, I just now created a new Leaders: District Roundtable series starting on 12/11 that is supposed to occur at 5p HST on the 2nd Wednesday of each month. When you go to the 3/12/25 event (and every other event in the series after Spring DST until the series ends on 7/9/25), it shows a start time of 4p HST. The same applies to the Leaders & Parents: Pack Committee Meeting series beginning on 12/15.
I changed nothing after creation of either of these. This suggests that the issue is in the recurring meeting creation logic and not a change after creation. The system must be adding or subtracting an hour at the moment of creation to compensate for DST. Unfortunately, that doesn’t work for Hawaii and Arizona where we don’t adjust for DST.
Side Note: While the developers are looking at this, I want to also mention that the system does other odd things based on time at creation. I originally tried to create these events at 7p HST (19:00:00), but received the following error message:
Error
toTime must be larger than or equal to fromTime - fromTime: 23:00:00 - toTime: 00:00:00
The 4 hour difference looks like the time is being converted to Central Standard Time before error checking is applied. Starting at 6p HST returned a different error message, even though the toDate in the form is clearly set to 5/31/25:
Error
The toDate must be the last day of current or any future month - toDate: 2025-06-01
Perhaps the date is keyed to Eastern time? For both series, I had to change it to 5p HST to get it to accept and I will now have to manually change each meeting in the series to 7p HST. (This reminds me that I hadn’t put them on the schedule before out of frustration).
If they could look into that too, I would be ecstatic. This one may be more the result of error checking that assumes Pacific-Atlantic time zones than a DST issue, but notably after I create the series I can change the time to 7p HST on each individual event manually.
Tell the developer I said thank you and good luck!
1 Like
Thank you. I have passed your message on.
2 Likes
@DaveMorris Can you please share a screen share for your second issue? Having trouble understanding the issue.
I don’t understand the question. Are you asking to do a video call for me to show you, or a screenshot of the errors I quoted above.
If the latter, I can’t access it now, but picture this:
-
You fill out the form to create a recurring event at 7p HST.
-
Click “Create Event”
-
The event does not save, the exact text I quoted avove pops up in a red box (in the web page, not external to it) with white letters, instead of the green box with the “success” message.
-
You change the time to 5p.
-
Click “Create Event”
-
The event saves and generates the success message.
Have you tried setting your PC to HST before attempting to replicate?
Was able to replicate. Will work the issue.
Thanks for the update.
Please let me know whether I need to leave the two Leader event series as they are or if you have enough info so that I can manually change each of those to 7pm. Thank you!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
@DaveMorris I missed your reply due to the holiday. Yes, you can change to 7pm. We are continuing to work the issue and will post the fix on the Scoutbook Plus change log when it is resolved.
1 Like
Dave, I wanted to follow up with you and see if your events were reflecting properly. We made a change on the back end that should resolve the issue with new event entry that is recurring over daylight savings time change. If you have any further issues. please reach out.
