Tech Forum

Posted: **Wed Nov 16, 2022 6:33 pm**

Still not loading for me. Will have to keep waiting I guess.

Posted: **Thu Nov 17, 2022 7:16 am**

Anyone have any idea how much longer the calendar feature is going to be down? I schedule literally hundreds of events each year as stake bldg scheduler with frequent funerals, receptions, Temple related activities, etc., (we have a Temple within our stake boundaries) and several new events needing to be scheduled each day. I cannot see the calendar for two days now and now have a backlog of scheduling requests. I’m getting a little panicked because our stake depends heavily on the calendar.

Posted: **Thu Nov 17, 2022 7:45 am**

I started https://tech.churchofjesuschrist.org/fo ... hp?t=41429 but a comment directed to this thread as well. Are there ever any replies from the Calendar team in these threads?

I have tried multiple browsers, incognito, and clearing my application cache/data but am seeing the following console error before getting the blank screen:

Code: Select all

POST https://ident.churchofjesuschrist.org/sso/json/sessions?_action=getSessionInfo 401
send @ jquery.js:8623
ajax @ jquery.js:8152
_.restCall @ ServiceInvoker.js:186
p.serviceCall @ AbstractDelegate.js:48
e @ SessionService.js:29
e @ SessionService.js:54
S.getLoggedUser @ RESTLoginHelper.js:85
o @ lodash.js:4935
e @ ModuleLoader.js:67
f.getLoggedUser @ SessionManager.js:41
(anonymous) @ CommonConfig.js:64
(anonymous) @ jquery.js:3230
l @ jquery.js:3073
fireWith @ jquery.js:3185
a.<computed> @ jquery.js:3275
(anonymous) @ i18next.js:144
e @ i18next.js:245
(anonymous) @ i18next.js:260
(anonymous) @ BackendConnector.js:144
e @ BackendConnector.js:122
(anonymous) @ BackendConnector.js:235
(anonymous) @ BackendConnector.js:175
(anonymous) @ index.js:94
s.onreadystatechange @ ajax.js:69
XMLHttpRequest.send (async)
o @ ajax.js:71
e @ index.js:82
e @ index.js:75
e @ BackendConnector.js:168
e @ BackendConnector.js:231
(anonymous) @ BackendConnector.js:200
e @ BackendConnector.js:199
e @ i18next.js:194
e @ i18next.js:259
e @ i18next.js:265
e @ i18next.js:139
setTimeout (async)
e @ i18next.js:151
b @ manager.js:56
e @ CommonConfig.js:63
(anonymous) @ ProcessConfiguration.js:26
(anonymous) @ EventManager.js:30
setTimeout (async)
(anonymous) @ EventManager.js:29
Sr @ lodash.js:639
hl @ lodash.js:9556
u.sendEvent @ EventManager.js:27
(anonymous) @ CommonConfig.js:100
(anonymous) @ SiteConfigurationService.js:40
(anonymous) @ jquery.js:3230
l @ jquery.js:3073
fireWith @ jquery.js:3185
(anonymous) @ jquery.js:3237
l @ jquery.js:3073
fireWith @ jquery.js:3185
a.<computed> @ jquery.js:3275
e @ ServiceInvoker.js:64
(anonymous) @ jquery.js:3230
l @ jquery.js:3073
fireWith @ jquery.js:3185
E @ jquery.js:8251
(anonymous) @ jquery.js:8598
load (async)
send @ jquery.js:8615
ajax @ jquery.js:8152
_.restCall @ ServiceInvoker.js:186
p.serviceCall @ AbstractDelegate.js:48
w @ ServerService.js:47
c.getConfiguration @ SiteConfigurationService.js:38
e @ CommonConfig.js:98
(anonymous) @ ProcessConfiguration.js:26
(anonymous) @ EventManager.js:30
setTimeout (async)
(anonymous) @ EventManager.js:29
Sr @ lodash.js:639
hl @ lodash.js:9556
u.sendEvent @ EventManager.js:27
y.loadEventHandlers @ ProcessConfiguration.js:33
(anonymous) @ main.js:30
o @ bootstrap:61
(anonymous) @ bootstrap:178
(anonymous) @ bootstrap:178
jquery.js:8623          POST https://ident.churchofjesuschrist.org/sso/json/realms/root/realms/church/authenticate?service=OktaOIDC&goto=https://www.churchofjesuschrist.org/services/platform/v4/set-wam-cookie&authIndexType=service&authIndexValue=OktaOIDC 401
send @ jquery.js:8623
ajax @ jquery.js:8152
_.restCall @ ServiceInvoker.js:186
p.serviceCall @ AbstractDelegate.js:48
C.submitRequirements @ AuthNService.js:164
C.getRequirements @ AuthNService.js:252
e @ RESTLoginView.js:302
(anonymous) @ ViewManager.js:64
Promise.then (async)
_ @ ViewManager.js:45
(anonymous) @ CommonConfig.js:188
Promise.then (async)
e @ CommonConfig.js:174
(anonymous) @ ProcessConfiguration.js:26
(anonymous) @ EventManager.js:30
setTimeout (async)
(anonymous) @ EventManager.js:29
Sr @ lodash.js:639
hl @ lodash.js:9556
u.sendEvent @ EventManager.js:27
e @ Router.js:130
yr @ lodash.js:476
s @ lodash.js:5323
execute @ backbone.js:1265
(anonymous) @ backbone.js:1254
(anonymous) @ backbone.js:1481
y.some.y.any @ underscore.js:286
loadUrl @ backbone.js:1479
start @ backbone.js:1445
b.init @ Router.js:136
e @ CommonConfig.js:51
f @ runtime.js:62
a @ runtime.js:288
e.<computed> @ runtime.js:114
n @ CommonConfig.js:44
(anonymous) @ CommonConfig.js:44
Promise.then (async)
n @ CommonConfig.js:44
(anonymous) @ CommonConfig.js:44
(anonymous) @ CommonConfig.js:44
t @ CommonConfig.js:49
(anonymous) @ jquery.js:3230
l @ jquery.js:3073
fireWith @ jquery.js:3185
(anonymous) @ jquery.js:3237
l @ jquery.js:3073
fireWith @ jquery.js:3185
a.<computed> @ jquery.js:3275
l @ jquery.js:3073
add @ jquery.js:3119
always @ jquery.js:3220
(anonymous) @ EventManager.js:30
setTimeout (async)
(anonymous) @ EventManager.js:29
Sr @ lodash.js:639
hl @ lodash.js:9556
u.sendEvent @ EventManager.js:27
(anonymous) @ CommonConfig.js:75
(anonymous) @ ModuleLoader.js:74
(anonymous) @ jquery.js:3230
l @ jquery.js:3073
fireWith @ jquery.js:3185
(anonymous) @ jquery.js:3237
l @ jquery.js:3073
fireWith @ jquery.js:3185
a.<computed> @ jquery.js:3275
t @ ServiceInvoker.js:88
(anonymous) @ jquery.js:3230
l @ jquery.js:3073
fireWith @ jquery.js:3185
E @ jquery.js:8253
(anonymous) @ jquery.js:8598
load (async)
send @ jquery.js:8615
ajax @ jquery.js:8152
_.restCall @ ServiceInvoker.js:186
p.serviceCall @ AbstractDelegate.js:48
e @ SessionService.js:29
e @ SessionService.js:54
S.getLoggedUser @ RESTLoginHelper.js:85
o @ lodash.js:4935
e @ ModuleLoader.js:67
f.getLoggedUser @ SessionManager.js:41
(anonymous) @ CommonConfig.js:64
(anonymous) @ jquery.js:3230
l @ jquery.js:3073
fireWith @ jquery.js:3185
a.<computed> @ jquery.js:3275
(anonymous) @ i18next.js:144
e @ i18next.js:245
(anonymous) @ i18next.js:260
(anonymous) @ BackendConnector.js:144
e @ BackendConnector.js:122
(anonymous) @ BackendConnector.js:235
(anonymous) @ BackendConnector.js:175
(anonymous) @ index.js:94
s.onreadystatechange @ ajax.js:69
XMLHttpRequest.send (async)
o @ ajax.js:71
e @ index.js:82
e @ index.js:75
e @ BackendConnector.js:168
e @ BackendConnector.js:231
(anonymous) @ BackendConnector.js:200
e @ BackendConnector.js:199
e @ i18next.js:194
e @ i18next.js:259
e @ i18next.js:265
e @ i18next.js:139
setTimeout (async)
e @ i18next.js:151
b @ manager.js:56
e @ CommonConfig.js:63
(anonymous) @ ProcessConfiguration.js:26
(anonymous) @ EventManager.js:30
setTimeout (async)
(anonymous) @ EventManager.js:29
Sr @ lodash.js:639
hl @ lodash.js:9556
u.sendEvent @ EventManager.js:27
(anonymous) @ CommonConfig.js:100
(anonymous) @ SiteConfigurationService.js:40
(anonymous) @ jquery.js:3230
l @ jquery.js:3073
fireWith @ jquery.js:3185
(anonymous) @ jquery.js:3237
l @ jquery.js:3073
fireWith @ jquery.js:3185
a.<computed> @ jquery.js:3275
e @ ServiceInvoker.js:64
(anonymous) @ jquery.js:3230
l @ jquery.js:3073
fireWith @ jquery.js:3185
E @ jquery.js:8251
(anonymous) @ jquery.js:8598
load (async)
send @ jquery.js:8615
ajax @ jquery.js:8152
_.restCall @ ServiceInvoker.js:186
p.serviceCall @ AbstractDelegate.js:48
w @ ServerService.js:47
c.getConfiguration @ SiteConfigurationService.js:38
e @ CommonConfig.js:98
(anonymous) @ ProcessConfiguration.js:26
(anonymous) @ EventManager.js:30
setTimeout (async)
(anonymous) @ EventManager.js:29
Sr @ lodash.js:639
hl @ lodash.js:9556
u.sendEvent @ EventManager.js:27
y.loadEventHandlers @ ProcessConfiguration.js:33
(anonymous) @ main.js:30
o @ bootstrap:61
(anonymous) @ bootstrap:178
(anonymous) @ bootstrap:178
Messages.js:88 error: Session has timed out {message: 'Session has timed out', type: 'error'}
useFetch.js:32          GET https://www.churchofjesuschrist.org/church-calendar/services/v3.0/mem/currentUserOptions?lang=eng 502
(anonymous) @ useFetch.js:32
(anonymous) @ useFetch.js:44
Ys @ react-dom.production.min.js:262
b @ scheduler.production.min.js:18
to @ react-dom.production.min.js:122
Us @ react-dom.production.min.js:261
(anonymous) @ react-dom.production.min.js:261
ne @ scheduler.production.min.js:16
o.register.$.port1.onmessage @ scheduler.production.min.js:12
9UX54-L57TE-34QD8-DURP5-GFD2R:10 TypeError: O.buildingSchedulerDtos is not iterable
    at CommonDataContext.js:74:46
    at Ys (react-dom.production.min.js:262:359)
    at b (scheduler.production.min.js:18:343)
    at to (react-dom.production.min.js:122:325)
    at Us (react-dom.production.min.js:261:308)
    at react-dom.production.min.js:261:215
    at ne (scheduler.production.min.js:16:224)
    at o.register.$.port1.onmessage (scheduler.production.min.js:12:346)
BOOMR_plugins_errors_console_error @ 9UX54-L57TE-34QD8-DURP5-GFD2R:10
bl @ react-dom.production.min.js:216
n.callback @ react-dom.production.min.js:216
Co @ react-dom.production.min.js:131
Sl @ react-dom.production.min.js:220
Bs @ react-dom.production.min.js:259
b @ scheduler.production.min.js:18
to @ react-dom.production.min.js:122
Ws @ react-dom.production.min.js:252
Ts @ react-dom.production.min.js:243
(anonymous) @ react-dom.production.min.js:123
b @ scheduler.production.min.js:18
to @ react-dom.production.min.js:122
ao @ react-dom.production.min.js:123
ro @ react-dom.production.min.js:122
Ys @ react-dom.production.min.js:263
b @ scheduler.production.min.js:18
to @ react-dom.production.min.js:122
Us @ react-dom.production.min.js:261
(anonymous) @ react-dom.production.min.js:261
ne @ scheduler.production.min.js:16
o.register.$.port1.onmessage @ scheduler.production.min.js:12
CommonDataContext.js:74 Uncaught TypeError: O.buildingSchedulerDtos is not iterable at https://www.churchofjesuschrist.org/calendar/index.9f0e3658.js:15:33912 at Ys (https://www.churchofjesuschrist.org/calendar/index.9f0e3658.js:1:114038) at b (https://www.churchofjesuschrist.org/calendar/index.9f0e3658.js:1:132125) at to (https://www.churchofjesuschrist.org/calendar/index.9f0e3658.js:1:54698) at Us (https://www.churchofjesuschrist.org/calendar/index.9f0e3658.js:1:113501) at https://www.churchofjesuschrist.org/calendar/index.9f0e3658.js:1:113412 at ne (https://www.churchofjesuschrist.org/calendar/index.9f0e3658.js:1:131545) at o.register.$.port1.onmessage (https://www.churchofjesuschrist.org/calendar/index.9f0e3658.js:1:130295)

Posted: **Thu Nov 17, 2022 9:47 am**

dawdaw wrote: ↑Thu Nov 17, 2022 7:16 am Anyone have any idea how much longer the calendar feature is going to be down?I cannot see the calendar for two days now and now have a backlog of scheduling requests. I’m getting a little panicked because our stake depends heavily on the calendar.

I am in the same boat as Stake Building Scheduler. I can at least see the calendar now thru hubby's account but that doesn't help me with
my calling. Had private events in the works getting approvals (received) and now unable to calendar. Before calendar update I did go in and put restrictions on calendar for pending events to block others from getting. Sure glad I did that.

Be sure to do feedback because this is a user-to-user help forum and not the official method for interacting with any kind of Church support.

Posted: **Thu Nov 17, 2022 9:58 am**

Thank you casper684!

Posted: **Thu Nov 17, 2022 10:38 am**

casper684 wrote: ↑Thu Nov 17, 2022 9:47 am Before calendar update I did go in and put restrictions on calendar for pending events to block others from getting.

Be aware that restrictions can't block someone else from the same unit from scheduling. For example, you put a restriction on the cultural hall for a RS activity for Ward A, No other ward can schedule an event. But that wouldn't block the YM from Ward A from scheduling it.

Posted: **Thu Nov 17, 2022 11:01 am**

Ah yes so true. But at least it narrowed it down to just the one ward and activity happens to be during the day.
So guess my work around until I can get access, though incorrect will be to have someone with
access place event on a little used calendar of that ward with a notation that it is a private event. I don't know what
else to do.

Posted: **Thu Nov 17, 2022 12:31 pm**

casper684 wrote: ↑Thu Nov 17, 2022 11:01 am Ah yes so true. But at least it narrowed it down to just the one ward and activity happens to be during the day.

True, better than nothing. But placing anything else on the calendar will block the event from being created.

It seems the old idea of a "Building Scheduler" as someone who handles all the scheduling is no longer valid with the introduction of the on-line calendar. The position was created because of the limitations of paper calendars. The "Building Scheduler" in the calendar system is really a supervisory position - there to deal with conflicts and whatnot. (Such as the EQP scheduling the gym every Saturday for basketball.) Units should be scheduling themselves. Once an event is on the calendar, the facility is blocked off.

At least that's how it worked in the old calendar. We'll have to see what the new version brings.

Posted: **Thu Nov 17, 2022 1:13 pm**

russellhltn wrote: ↑Thu Nov 17, 2022 12:31 pm It seems the old idea of a "Building Scheduler" as someone who handles all the scheduling is no longer valid with the introduction of the on-line calendar. The position was created because of the limitations of paper calendars. The "Building Scheduler" in the calendar system is really a supervisory position - there to deal with conflicts and whatnot. (Such as the EQP scheduling the gym every Saturday for basketball.) Units should be scheduling themselves. Once an event is on the calendar, the facility is blocked off.

At least that's how it worked in the old calendar. We'll have to see what the new version brings.

Not every auxiliary presidency wishes to do their own scheduling or to take the time to learn how to do it. Some do it, but they do it incorrectly. I always encourage the leaders to do their own scheduling, but it rarely happens.

Posted: **Thu Nov 17, 2022 2:45 pm**

margiestroble wrote: ↑Thu Nov 17, 2022 1:13 pm Not every auxiliary presidency wishes to do their own scheduling or to take the time to learn how to do it. Some do it, but they do it incorrectly. I always encourage the leaders to do their own scheduling, but it rarely happens.

Understood. However, it works better if at least the unit does their own scheduling. (Perhaps a clerk or secretary.) That way the event appears to the members of the unit. Things quickly get convoluted when someone outside the ward is tagged with scheduling.

Tech Forum

"All Day" Calendar Events Set to 3 Days (instead of 1) - for 11 March 2023 and beyond!

Re: "All Day" Calendar Events Set to 3 Days (instead of 1) - for 11 March 2023 and beyond!

Re: "All Day" Calendar Events Set to 3 Days (instead of 1) - for 11 March 2023 and beyond!

Re: "All Day" Calendar Events Set to 3 Days (instead of 1) - for 11 March 2023 and beyond!

Re: "All Day" Calendar Events Set to 3 Days (instead of 1) - for 11 March 2023 and beyond!

Re: "All Day" Calendar Events Set to 3 Days (instead of 1) - for 11 March 2023 and beyond!

Re: "All Day" Calendar Events Set to 3 Days (instead of 1) - for 11 March 2023 and beyond!

Re: "All Day" Calendar Events Set to 3 Days (instead of 1) - for 11 March 2023 and beyond!

Re: "All Day" Calendar Events Set to 3 Days (instead of 1) - for 11 March 2023 and beyond!

Re: "All Day" Calendar Events Set to 3 Days (instead of 1) - for 11 March 2023 and beyond!

Re: "All Day" Calendar Events Set to 3 Days (instead of 1) - for 11 March 2023 and beyond!