@NateWr Thanks. Now I’m on a different computer (a 2012 Mac with latest OS, Safari and Firefox).
On Safari I have not seen the ##api.submissions.unknownError## message, just the javascript errors I noted above. It’s possible that the message just disappears too quickly to see; on Firefox it pops up (in a little window) and goes away so quickly that I had to record the screen to read it.
From now on I’m running Firefox 59.0.2. The cache is turned off and I have the Developer Console open.
-
Just navigating to the login page, without logging in, gives “
Empty string passed to getElementById(). jquery.js:2778:12” That script comes from ajax.googleapis.com. -
Login as journal manager, no messages and everything looks normal.
-
Logout (without doing anything). About 2 in every 3 times, the ##api.submissions.unknownError## message pops up for a moment and the console says
TypeError: $handledElement is undefined ModalHandler.js:214:3
TypeError: $handledElement is undefined ModalHandler.js:204:4
TypeError: $handledElement is undefined ModalHandler.js:210:4
Looking in the Network tab, there is a status 302 GET for file “signOut”. Otherwise there are only 200s. There are no XHR requests shown at all. -
Now login again. Nothing happens if I just wait. Everything looks normal.
-
Select Settings->Journal. About 3 in every 4 times the message ##api.submissions.unknownError## pops up for a moment and the same 3 js errors appear. Going backwards and forwards from the initial view to Settings->Journal produces the same errors (but not every time). Now I see 4 XHR GET requests (all 200) and one XHR POST request (also 200).
-
Logout, login. tabs Unassigned, All Active, and Archives all bring up lists without any errors noted. Now there is one more XHR request (fetch-grid, status 200).
What else can I try? Brendan.