Hi @Stephen_Hornak! Thanks for your feedback. I only wish the solution were that simple! I have already invested countless HOURS with @GoDaddy support trying to troubleshoot this. Not only are they completely unhelpful, they just want to point fingers back to the Scoutbook source and/or suggest we move to a Google Calendar, which is not practical (or something we even want to consider). I have extensively tried using their online self-help ( knowledge base), AI, live chat (India) and even got a supervisor on the phone in the Philippines, all without any progress. In addition to providing an overall poor support experience, the real problem with GoDaddy is that nobody I have interacted with (so far) actually knows how shared / subscribed calendars work (or will take the time to learn / test with me). All they do is read their Wiki and keep sending me the following link which is not helpful:
Despite my best efforts to isolate and troubleshoot myself, I cannot clearly tell if the issue lies with GoDaddy or Scoutbook, and as I said before, everything worked PERFECTLY up until last week (at least when we noticed). As I am seeing more here about all of the ongoing changes happening with the calendar system, it gives me some concern that the issue may lie there instead, but I remain open to all options, and obviously just want to get this fixed for the benefit of the pack I am trying to help.
By posting this thread, my hope is/was to get some input from a.) those who oversee / implement the ongoing calendar changes, such as @edavignon, @suacinformation or others; and, b.) from others like @ChristopherCamacho who have previously reported the same problem and obviously found a way to fix it (I just want to know “how”):
https://troop230.net/troop-calendar
Any and all additional help from the community here is graciously welcome. Thank you.
