{"ops":[{"insert":"I have a Google Sheets file with links to various decks on Archidekt. I store them as a list of links copied from the \"share\" option from the website.\nSo far I had no problems using those links but recently (I think since the collaborator option was added) they stopped working. Instead, a \"deck not found\" error is displayed.\n\nIt looks like the page tries to load the deck before it checks if I am logged in. Refreshing the page does not solve the issue even though the website shows that I am logged in though.\nAlso, when I copy the address from the \"deck not found\" page to a new tab in the same web browser, it loads correctly, so I don't think it's an issue with text formatting of the links or anything like that.\nIt does not seem to make a difference if there is a #Deck_name and the end or not.\n\nFrom my observations it affect all of my decks that are set to Private, even if I am logged in a different tab before clicking on the link.\nNo issues with using links from the same list to decks that are not set to Private.\n\nPlease see attached screenshots displaying the issue - as you can see the link is exactly the same and I am logged to the same account.\n\n"},{"insert":{"image":"https://i.imgur.com/vuOXh8e.jpg"}},{"insert":"\n"},{"insert":{"image":"https://i.imgur.com/FHoV2g1.jpg"}},{"insert":"\n"}]}
0
{"ops":[{"insert":"Alrighty so here's what's happening here, it's a bit technical so bare with me on this. \n\nThe reason this is happening is because we migrated how the site is rendered to rely more on standard browser authentication methods. What this means is that when you load a link on Archidekt, your browser should send along your cookie as it's making the request. \n\nOn redirects however, cookies aren't sent by the browser.\n\nThis is important to note because google drive (tested it in sheets, and docs) seems to not open new links, but rather redirect the link internally (probably for some telemetry data or whatnot, who knows). \n\nSo what does this mean for you? Well, because your auth data (your cookie) isn't sent on a redirect, private decks will end up 404ing because the server doesn't think you have access to the deck (because it's private, and your auth wasn't sent). We know this is the case because when you get that 404, if you just immediately refresh the page, the page will load correctly. \n\nSo what can we do about it? I'll look into seeing if there's a way we can fix this on our end. Usually this kind of behavior is easily capturable because under normal circumstances the page that's being loaded can know if it's private or not before actually checking your auth, so it can know to reload the page without the redirect. In our case, since decks can be both private "},{"attributes":{"italic":true},"insert":"and "},{"insert":"public, that's a bit more difficult. Either way, we'll look into it. \n\nFor now though, just hit ctrl/cmd+r when you end up getting a 404 and the page should load normally. \n\ntl;dr - Google drive seems to be redirecting to external links in a slightly less than standard way which is the cause for the issue. Hit ctrl/cmd+r once Archidekt loads and it should load fine at that point. Hopefully that'll get your workflow up and running for now while we look into if it's possible to fix this. \n\nThanks for the heads up, and sorry for the trouble!\n"}]}
1
{"ops":[{"insert":"Hey, thanks for looking into this!\n\nI would totally understand if that's not something you can solve in a reasonable fashion, especially if that's limited to Google docs.\n\nThe Ctrl+R does not seem to work, but I'll manage.\n\nAnd thanks for the background info as well, that was actually interesting to read for me. :)\n"}]}
0