MelffyBunilla 4 years{"ops":[{"insert":"Since this newer version of Archidekt I have the issue that my sorting settings aren't applied correctly when logging in to archidekt (with a new browser session). Basically it sorts by default and shows the pricing by default (sorting by alphabet, pricing by CK). In prior versions I often just had to do a Ctrl + F5 to get my account settings, but now the only way to \"fix\" it for the browser session seems to be to open my account settings (I don't have to change anything, just navigate to them), and then refresh the decklist I'm working on. Is this a known issue?\n"}]}
0
Jeremy(Archidekt Moderator)
4 years{"ops":[{"insert":"We've received reports of this from a few users, but have yet to nail down exactly what's going on. At the moment, we're just trying to find what link those experiencing it. What browser are you using? \n\nRegardless, I apologize for the inconvenience. This is one of our top priorities to get figured out right now so hopefully we'll have a fix soon!\n"}]}
0
MelffyBunilla 4 years{"ops":[{"insert":"Hi Jeremy\n\nSo I'm using Google Chrome on Windows 11, and I did a few more tests, maybe they help (I'm a web developer, so I did a few basic tests to see what your page does):\nYou seem to store the account settings in a cookie which later is then referenced when opening a decklist (for example the deckSorting + an integer to define what the user has as a setting for that)"},{"attributes":{"list":"ordered"},"insert":"\n"},{"insert":"When navigating to archidekt with a fresh browser session, and login in, it calls /login, which in return gets a token which contains the values you store in the cookie, so when I use login while I am on a decklist, it then sorts them right away. However it does not store that token as a cookie, so when I reload the webpage, the settings are not there, and your functions call the default functions (the ones that are also called when I am not logged in)"},{"attributes":{"list":"ordered"},"insert":"\n"},{"insert":"When navigating to the account settings however, it does add the cookie to my browser session, from which point onwards the decklists are displayed correctly"},{"attributes":{"list":"ordered"},"insert":"\n"},{"insert":"You call a /private page when updating those settings from that page"},{"attributes":{"list":"ordered"},"insert":"\n"},{"insert":"\nSo it seems by these basic tests that there is an issue initializing the cookie for the browser session when first login in, which does not seem to have the same issue when going to the account settings themselves\n"}]}
0