Llyarden Posted May 15, 2023 Clone Share Posted May 15, 2023 I don't know exactly what causes this, but this is the second time it's happened in the same thread now so I figure I might mention it on the offchance that it can be fixed. I have a thread here (in a private game), and it has the link to my sheet, as is fairly normal. Now the problem is that sometimes I click on that link and it...doesn't actually take me to my sheet. Instead it takes me to my sheets list. Both times it's happened, the next time I click on exactly the same link in the same tab, it loads my sheet correctly. And most of the time it works entirely normally without doing this at all! The link I have it set to take me to is: https://test.myth-weavers.com/sheets/?id=2788080 But instead the link it sends me to is: https://test.myth-weavers.com/sheets/?code=7f6a68fcd598c1991e52161bd06d153340b4b9a767de55d09a3f2ca792726f24 I've double-checked the source code and the only oddity I can notice is that Invision has added a 'rel=""' block in the anchor tag for some reason, but nothing to suggest why I'd end up in an entirely different place. Link to comment Share on other sites More sharing options...
Eric Posted May 15, 2023 Clone Share Posted May 15, 2023 The code link is an intermediate step in the authorization process for the sheets viewer. The fact that it's stopping there probably means that something went wrong; if it happens again, there are likely some error messages in the Javascript console that will help @Rodrigo and myself diagnose the issue. Link to comment Share on other sites More sharing options...
Llyarden Posted May 15, 2023 Author Clone Share Posted May 15, 2023 (edited) Okay, I didn't see any when I went back and looked at the console but I think I might have already gone back and forth in my browser history by that point so they might have been cleared. EDIT: It seems I can reproduce this by clearing my MW cookies - I did see some sort of message pop up in the console very briefly, but the redirect from the sheet url to the code link was too quick for me to see what it was. The only console output that showed up at the code link was: [NoScript]:0 Prompt Hook installation https://test.myth-weavers.com/sheets//?id=2788080 Which might be my addon. Edited May 15, 2023 by Llyarden (see edit history) Link to comment Share on other sites More sharing options...
Eric Posted May 15, 2023 Clone Share Posted May 15, 2023 Put *.myth-weavers.com on your whitelist? Link to comment Share on other sites More sharing options...
Llyarden Posted May 15, 2023 Author Clone Share Posted May 15, 2023 (edited) It already is (the whole site doesn't work if it isn't.) And now even though as far as I'm aware nothing has changed, even by clearing my cookies I can't reproduce the issue any more, whether or not the addon is enabled or not. Edited May 15, 2023 by Llyarden (see edit history) Link to comment Share on other sites More sharing options...
Llyarden Posted May 23, 2023 Author Clone Share Posted May 23, 2023 (edited) Okay, it happened again, and this time I at least managed to find an error message. Not sure how useful an error message it is though or if it's even related, I don't remember seeing this any of the previous times: SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data e https://test.myth-weavers.com/sheets/index.js:2 postLogin https://test.myth-weavers.com/sheets/index.js:2 AuthProvider https://test.myth-weavers.com/sheets/index.js:2 AuthProvider https://test.myth-weavers.com/sheets/index.js:2 And it...didn't copy the exact point in the code for some reason even though that was in the message and I told it to copy the whole thing. That was 'index.js:2:1148033' Edited May 23, 2023 by Llyarden (see edit history) Link to comment Share on other sites More sharing options...
Eric Posted May 23, 2023 Clone Share Posted May 23, 2023 @Rodrigo, I summon you! Link to comment Share on other sites More sharing options...
Eric Posted November 15, 2023 Clone Share Posted November 15, 2023 Didn't previously mark this closed, but we did implement a fix for this problem. Link to comment Share on other sites More sharing options...
Recommended Posts