Next/Previous card sometimes uses secondary category instead of primary

 avatar
{"ops":[{"attributes":{"bold":true},"insert":"How to reproduce:"},{"insert":"\nGo to a deck with cards that are in multiple categories (e.g. https://archidekt.com/decks/12625201)"},{"attributes":{"list":"ordered"},"insert":"\n"},{"insert":"Enable multiple categories"},{"attributes":{"list":"ordered"},"insert":"\n"},{"insert":"Pick a card"},{"attributes":{"list":"ordered"},"insert":"\n"},{"insert":"Continuously use the previous/next option"},{"attributes":{"list":"ordered"},"insert":"\n"},{"insert":"\n"},{"attributes":{"bold":true},"insert":"Expected result:"},{"insert":"\nThe user can go through every card in the deck by pressing the next card button repeatedly. \n\n"},{"attributes":{"bold":true},"insert":"Actual result:"},{"insert":"\nThe user will end up in 'loops' of the same few cards.\n\n"},{"attributes":{"bold":true},"insert":"Proposed fix:"},{"insert":"\nOnly use the primary category when using the previous/next card buttons. \n"}]}
Edited 4/30/2025, 9:31:27 AM
0
 avatar
{"ops":[{"insert":"This is a known issue, and it's been marked as won't fix. The only time this occurs is when using categories (multiple) as the group by, and we'd need to keep track of a secondary odering unique to that layout. In a perfect world this would be fixed, but in reality it's probably not worth the extra complexity + development costs to build an entirely separate next/ previous functionality for a single layout.\n"}]}
1