{"ops":[{"insert":"I accidentaly duplicated a card catrgory while managing my own stacks.\nThis happened when I tried to move a category and it sloted \"on top of\" another category, duplicated itself into the \"new\" and \"old\" stack.\n\nPasted the error report here\n\nError: Cannot have two MultiBackends at the same time.\n at eQ (https://cdn.archidekt.com/_next/static/chunks/pages/_app-6ba36ff8f043aca0.js:10:695725)\n at div\n at div\n at e3 (https://cdn.archidekt.com/_next/static/chunks/pages/_app-6ba36ff8f043aca0.js:10:697163)\n at https://cdn.archidekt.com/_next/static/chunks/2390-aa25d8aa2692a218.js:5:26363\n at n.Z (https://cdn.archidekt.com/_next/static/chunks/2730-a31c34ec01e9a170.js:1:202)\n at div\n at sz (https://cdn.archidekt.com/_next/static/chunks/6702-3c617a064836a27f.js:1:253176)\n at s6 (https://cdn.archidekt.com/_next/static/chunks/6702-3c617a064836a27f.js:1:257566)\n at r (https://cdn.archidekt.com/_next/static/chunks/pages/_app-6ba36ff8f043aca0.js:10:414665)\n at eC (https://cdn.archidekt.com/_next/static/chunks/pages/_app-6ba36ff8f043aca0.js:101:554985)\n at l (https://cdn.archidekt.com/_next/static/chunks/pages/_app-6ba36ff8f043aca0.js:10:787201)\n at R (https://cdn.archidekt.com/_next/static/chunks/pages/_app-6ba36ff8f043aca0.js:93:498)\n at t (https://cdn.archidekt.com/_next/static/chunks/pages/_app-6ba36ff8f043aca0.js:10:413701)\n at K (https://cdn.archidekt.com/_next/static/chunks/pages/_app-6ba36ff8f043aca0.js:10:417450)\n at t.PathnameContextProviderAdapter (https://cdn.archidekt.com/_next/static/chunks/main-6c8be007138b1c74.js:1:42723)\n at i (https://cdn.archidekt.com/_next/static/chunks/main-6c8be007138b1c74.js:1:7026)\n at et (https://cdn.archidekt.com/_next/static/chunks/main-6c8be007138b1c74.js:1:8905)\n at el (https://cdn.archidekt.com/_next/static/chunks/main-6c8be007138b1c74.js:1:11850)\n"}]}
0
{"ops":[{"insert":"Sorry for the trouble! Unfortunately, this is a known bug related to controlled stacks that can occur if you're moving categories about in the controlled view too quickly. Definitely not your fault of course, but moving a bit more deliberately in the future should prevent it from happening again.\n\nAs for how to fix the deck this has occurred in, it's fortunately just a visual bug stored in your local cache. If you're in Chrome or Firefox, click the lock icon to the left of the deck URL in your browser nav bar. From there, you'll want to \"clear cookies and site data\" for Archidekt. It'll log you out, but once logged back in, you shouldn't see the duplicated stack anymore.\n\nI apologize for the inconvenience! Ideally controlled stacks would be more tolerant of faster use, but it's not something we have an immediate fix for. Please let me know if this gives you any further trouble.\n"}]}
0
{"ops":[{"insert":"No problem, reseting the cache helped and is a nice fix.\nIf patience was as easy... ;)\n\nThanks\n"}]}
0