# iCal/ICS Calendar Subscription - Incorrectly Displaying in Zulu Time on GoDaddy Website

**URL:** <https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667>\
**Category:** New Calendar Bugs\
**Tags:** calendar, scoutbook\
**Created:** [January 30, 2024, 12:12am UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667 "2024-01-30T00:12:56Z")\
**Posts on this page:** 18\
**Page:** 2

<div class="post-metadata">

**Author:** ![edavignon](https://sea2.discourse-cdn.com/scouting/user_avatar/discussions.scouting.org/edavignon/32/16_2.png) [@edavignon](https://discussions.scouting.org/u/edavignon)\
**Post date:** [January 31, 2024, 2:40pm UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667/21 "2024-01-31T14:40:40Z")

</div>

@BraunMincher

Thank you for the debug information. I have passed this on to the IA developers.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/scouting/original/1X/66e9612584db5dbf76de17f00ad877998c0ba3d6.png) [@system](https://discussions.scouting.org/u/system)\
**Post date:** [February 1, 2024, 2:40pm UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667/22 "2024-02-01T14:40:42Z")

</div>

Closed on February 1, 2024, 2:40pm UTC

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![DonovanMcNeil](https://sea2.discourse-cdn.com/scouting/user_avatar/discussions.scouting.org/donovanmcneil/32/24_2.png) [@DonovanMcNeil](https://discussions.scouting.org/u/DonovanMcNeil)\
**Post date:** [February 6, 2024, 4:02pm UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667/23 "2024-02-06T16:02:34Z")

</div>

@BraunMincher I will send you a direct message \> look at top right Avatar to find it \> it will be a green envelope \> it will be a private message channel with select members of the Scoutbook User Advisory Council (SUAC)

---

<div class="post-metadata">

**Author:** ![DonovanMcNeil](https://sea2.discourse-cdn.com/scouting/user_avatar/discussions.scouting.org/donovanmcneil/32/24_2.png) [@DonovanMcNeil](https://discussions.scouting.org/u/DonovanMcNeil)\
**Post date:** [February 6, 2024, 4:02pm UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667/24 "2024-02-06T16:02:45Z")

</div>

Opened on February 6, 2024, 4:02pm UTC



---

<div class="post-metadata">

**Author:** ![MichaelWilliams14](https://avatars.discourse-cdn.com/v4/letter/m/f17d59/32.png) [@MichaelWilliams14](https://discussions.scouting.org/u/MichaelWilliams14)\
**Post date:** [July 1, 2024, 1:46pm UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667/26 "2024-07-01T13:46:09Z")

</div>

I have the same issue - it still exists. (Glad to have found this post!)  
 → The old scoutbook calendar URLs are no longer supported and do not work.  
 → The newer Scoutbook Plus URL shows as four hours ahead.  
Has the SUAC made any progress on updating the time zone embedded in the URLs, or is this on a roadmap for future implementation?

---

<div class="post-metadata">

**Author:** ![Stephen\_Hornak](https://sea2.discourse-cdn.com/scouting/user_avatar/discussions.scouting.org/stephen_hornak/32/16282_2.png) [@Stephen\_Hornak](https://discussions.scouting.org/u/Stephen_Hornak)\
**Post date:** [July 1, 2024, 1:50pm UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667/27 "2024-07-01T13:50:08Z")

</div>

@MichaelWilliams14 - have you checked the time zone settings in [scoutbook.scouting.org](http://scoutbook.scouting.org) and [advancements.scouting.org](http://advancements.scouting.org). Our calendar subscriptions show the correct time.

 ![image](https://global.discourse-cdn.com/scouting/original/3X/6/9/69f78a4ee93abe0a9b84b363d1062114721b069f.png)

 ![image](https://global.discourse-cdn.com/scouting/original/3X/7/d/7d80b4f9ae10bd2c23614d81f686e3fac33c80d5.png)

If this is related to godaddy, the issue is that their calendar is unable to properly handle the url. Goggle has no problem with it.

---

<div class="post-metadata">

**Author:** ![CharleyHamilton](https://sea2.discourse-cdn.com/scouting/user_avatar/discussions.scouting.org/charleyhamilton/32/3113_2.png) [@CharleyHamilton](https://discussions.scouting.org/u/CharleyHamilton)\
**Post date:** [July 1, 2024, 2:06pm UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667/28 "2024-07-01T14:06:36Z")

</div>

> [@MichaelWilliams14](#):
>
> Has the SUAC made any progress on updating the time zone embedded in the URLs

Just as a point of clarification, the SUAC folks are just volunteer scouters. They are not actually the ones who are doing the development.

---

<div class="post-metadata">

**Author:** ![MichaelWilliams14](https://avatars.discourse-cdn.com/v4/letter/m/f17d59/32.png) [@MichaelWilliams14](https://discussions.scouting.org/u/MichaelWilliams14)\
**Post date:** [July 1, 2024, 2:23pm UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667/29 "2024-07-01T14:23:57Z")

</div>

Charlie - thanks, I meant whoever is managing the site, not SUAC.

Stephen - Understood. Timezones are set in both sites. Google does display the calendar correctly, but GoDaddy does not.

While therefore I suspect the issue is on Godaddy’s side, from BraunMichner’s posts above, it sounds like the [adv.scouting.org](http://adv.scouting.org) link was sharing as “zulu” time. Not sure if this is still the case (and Google just interprets it differently) or if the issue truly is on Godaddy’s side.

---

<div class="post-metadata">

**Author:** ![Stephen\_Hornak](https://sea2.discourse-cdn.com/scouting/user_avatar/discussions.scouting.org/stephen_hornak/32/16282_2.png) [@Stephen\_Hornak](https://discussions.scouting.org/u/Stephen_Hornak)\
**Post date:** [July 1, 2024, 2:36pm UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667/30 "2024-07-01T14:36:55Z")

</div>

@MichaelWilliams14 - well here is the thing… if google gets it right, then it is a godaddy issue.

---

<div class="post-metadata">

**Author:** ![MichaelWilliams14](https://avatars.discourse-cdn.com/v4/letter/m/f17d59/32.png) [@MichaelWilliams14](https://discussions.scouting.org/u/MichaelWilliams14)\
**Post date:** [July 1, 2024, 5:09pm UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667/31 "2024-07-01T17:09:21Z")

</div>

Stephen - Maybe it’s a GoDaddy issue, maybe not. This wasn’t an issue with the older SB links. It is now an issue with the new links.

The above poster (Braun) said the new events each have “Zulu” (GMT) time added to each events’ code. I suspect Google and iCal may be smart enough to change to the user’s time zone or something, which is why they work. GoDaddy leaves it at Zulu.

Who might be able to confirm if those are still in the code of each event, or whether that has been fixed? (Or is that correct formatting of an event?)

FYI for anyone else seeing this with similar issues… GoDaddy customer service wants us to upgrade ($180/year) our account so we can use the “Appointments” feature to manage time zones. (The timezone is already correctly set to EST). What frustrates me is if the event code is right and Google/iCal read it correctly, it sounds like GoDaddy’s code must be “breaking” the code to change to GMT, then charging to fix the issue. (But perhaps I don’t understand the technical side.) Regardless, I did not upgrade/pay to discover whether the upgrade works or not.

If anyone else has run up against this and found a solution, please post.

---

<div class="post-metadata">

**Author:** ![Stephen\_Hornak](https://sea2.discourse-cdn.com/scouting/user_avatar/discussions.scouting.org/stephen_hornak/32/16282_2.png) [@Stephen\_Hornak](https://discussions.scouting.org/u/Stephen_Hornak)\
**Post date:** [July 1, 2024, 5:16pm UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667/32 "2024-07-01T17:16:07Z")

</div>

@MichaelWilliams14 - let me rephrase this for you… if all internet calendars can subscribe to the url and the times be correct EXCEPT for godaddy, what would that tell you. You would be better served by inserting thee google calendar in your site rather then rely on the godaddy version.

---

<div class="post-metadata">

**Author:** ![Matt.Johnson](https://sea2.discourse-cdn.com/scouting/user_avatar/discussions.scouting.org/matt.johnson/32/23672_2.png) [@Matt.Johnson](https://discussions.scouting.org/u/Matt.Johnson)\
**Post date:** [July 1, 2024, 6:38pm UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667/33 "2024-07-01T18:38:37Z")

</div>

> [@MichaelWilliams14](#):
>
> Stephen - Maybe it’s a GoDaddy issue, maybe not. This wasn’t an issue with the older SB links. It is now an issue with the new links.

It works for google, Apple, and Microsoft. It is a GoDaddy issue.

---

<div class="post-metadata">

**Author:** ![BraunMincher](https://sea2.discourse-cdn.com/scouting/user_avatar/discussions.scouting.org/braunmincher/32/24728_2.png) [@BraunMincher](https://discussions.scouting.org/u/BraunMincher)\
**Post date:** [July 1, 2024, 7:09pm UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667/34 "2024-07-01T19:09:58Z")

</div>

> [@BraunMincher](#):
>
> I think that I have identified the source of the time zone problem, and wanted to provide some details here both to document it for anyone else and also in hopes that the IA developers might read this and ultimately implement a fix. In short, the “ICS” link code from the legacy version of Scoutbook DOES correctly contain Time Zone (TZ) information, but the “API” link file from the newer IA (Internet Advancement) platform calendar does NOT, and instead only uses “Z” (Zulu / UTC). I think that most calendar programs (i.e. Apple/IOS, Google Calendar, Outlook, etc.) are smart enough to adjust for this, but when using something like “Calendar Display” from GoDaddy on website, the data is just “raw,” meaning that it incorrectly displays as UTC/Zulu (which in our case is Mountain Time +7 hours right now).

As the person who initially created this thread back at the beginning of the year, I will tell you that this whole “time zone” display issue has caused much frustration and wasted time. Sadly, I am not surprised that so many others are having the same problem (several have emailed me directly), but I think we have all come to the same conclusion – while the previous (legacy) SB calendar links MADE ADJUSTMENTS to the local time zones (to set them to whatever the pack/troop/unit setup in the portal), the new (“IA”) calendar links do NOT, and instead pass on the raw Zulu / GMC / UTC times to whatever program you are using to display them. EVERYONE _except_ the great folks at GoDaddy (note: sarcasm) have logic that is smart enough to “fix” this for the end users (when displayed), but GD does not, and so for all of us who are ‘beholden’ to them for our websites, we experience the same display problem documented above.

I am no longer an official pack leader (but was previously the Committee Chair), but one of the more ‘technically minded’ of our pack implemented the following fix for us back in April, which works for the time being with the new IA feed (but, unfortunately, I do not have any further details or specifics to share of “how” exactly this was programmed):

_Wrote a quick script and hosted it in Google cloud. When it receives a request from our events page it downloads the calendar from IA and adds the missing time zone info before serving it._

Yeah, this is certainly a shortcoming (IMHO) of GoDaddy’s inflexibility, but for all practical purposes, it seems that it would be best (easiest?) if the developers for the “new and improved” Scoutbook could just deliver the new ICS files WITH the time zone ALREADY ADJUSTED to match the pack or troop local time settings (since they did this before just fine…).

Sorry for everyone else who is experiencing this issue and hope that someone figures out a fix that can practically be applied to all units (that does not involve the behemoth of GoDaddy or other world powers…). May the force be with you!

Braun Mincher  
Erie, Colorado

---

<div class="post-metadata">

**Author:** ![edavignon](https://sea2.discourse-cdn.com/scouting/user_avatar/discussions.scouting.org/edavignon/32/16_2.png) [@edavignon](https://discussions.scouting.org/u/edavignon)\
**Post date:** [July 1, 2024, 7:26pm UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667/35 "2024-07-01T19:26:42Z")

</div>

Google, Apple and Microsoft all properly translate UTC to the local user’s Time Zone. BSA IT will not be expending resources to implement a change to workaround GoDaddy’s issue.

GoDaddy will need to fix the issue or units will need to find an alternate platform to host a calendar subscribed to the Scoutbook Plus calendar.

---

<div class="post-metadata">

**Author:** ![BraunMincher](https://sea2.discourse-cdn.com/scouting/user_avatar/discussions.scouting.org/braunmincher/32/24728_2.png) [@BraunMincher](https://discussions.scouting.org/u/BraunMincher)\
**Post date:** [July 1, 2024, 7:48pm UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667/36 "2024-07-01T19:48:23Z")

</div>

Ahh… good luck with that. From a practical standpoint, I think everyone knows that is not going to happen. Yes, GoDaddy is deficient in their technology strategy here, but I would respectfully argue that BSA IT made this work BEFORE (in the legacy ICS links), but broke it (by not considering it) in the new version. It’s tough to take away functionality that previously worked flawlessly for so many.

While we have a unique solution here for our individual unit (and I am but a lowly parent/volunteer, so take my response here with a grain of salt), practically and objectively speaking, the best overall solution here (least resources / most benefit to the masses) would certainly be for BSA IT to re-write the several lines of code (?) in the new calendar links that they took out of the old ones (and everything will work again…). Considering how many units – across the country/globe – have long ago implemented the GoDaddy calendar display (via their website template), and the lack of technical resources generally available at the pack level, I am of the subjective opinion that the fix here lies with BSA IT (rather than GoDaddy).

---

<div class="post-metadata">

**Author:** ![edavignon](https://sea2.discourse-cdn.com/scouting/user_avatar/discussions.scouting.org/edavignon/32/16_2.png) [@edavignon](https://discussions.scouting.org/u/edavignon)\
**Post date:** [July 1, 2024, 7:50pm UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667/37 "2024-07-01T19:50:11Z")

</div>

BSA IT has told me they will NOT workaround GoDaddy’s issue. The calendar implementation is following the standard used by the major calendar vendors.

I am closing this thread because no amount of arguing will change the position.

---

<div class="post-metadata">

**Author:** ![edavignon](https://sea2.discourse-cdn.com/scouting/user_avatar/discussions.scouting.org/edavignon/32/16_2.png) [@edavignon](https://discussions.scouting.org/u/edavignon)\
**Post date:** [July 1, 2024, 7:50pm UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667/38 "2024-07-01T19:50:25Z")

</div>

Closed on July 1, 2024, 7:50pm UTC



---

<div class="post-metadata">

**Author:** ![MichaelWilliams14](https://avatars.discourse-cdn.com/v4/letter/m/f17d59/32.png) [@MichaelWilliams14](https://discussions.scouting.org/u/MichaelWilliams14)\
**Post date:** [July 1, 2024, 7:53pm UTC](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667/39 "2024-07-01T19:53:27Z")

</div>

Braun - thanks so much. What a help/relief to just better understand what is causing the issue.  
If the correct formatting of a calendar event doesn’t include the timezone, I get why BSA wouldn’t want to add it - could cause future issues/break other “correct” things elsewhere. Your former unit’s solution (using a script to add the timezone info) makes sense. I’ll see if we have someone more technical who might be able to experiment with this, and in the off chance we do and figure something out, I’ll post what details/instructions I can here for anyone in a similar situation who stumbles across this post.

[Previous page](https://discussions.scouting.org/t/ical-ics-calendar-subscription-incorrectly-displaying-in-zulu-time-on-godaddy-website/400667.md?page=1)
