DecksMD 2.6.1

Decks 2.6.1 — suspended cards stay suspended

This release fixes the long-standing bug where suspended (and buried) cards reappeared in the review queue, most visibly after a plugin update.

Why it happened

Suspend and bury flags were stored only on the card's database row. Three code paths could rebuild or overwrite that row without carrying the flags along: the database rebuild that runs on plugin updates, the multi-device database merge, and an edge case in cross-device change replay. Review history always survived these paths — the suspend flag did not, so cards came back as reviewable.

What changed

Suspend and bury state now lives in its own preserved table, alongside review history and card identity bindings. It survives plugin updates, card edits, deleting and re-adding a card, and multi-device merges. When two devices disagree, the most recent change wins — suspending on one device and unsuspending later on another resolves to the later action.

One-time caveat

State that earlier versions already lost cannot be restored — there is nothing left to restore it from. Cards suspended after installing this update keep their state from then on. If your suspended cards were reset by a previous update, re-suspend them once (Browse → select → Suspend).

Also

• Resetting a card now clears its suspend/bury state on all devices consistently.
• A suspend synced from another device now applies even if the card was edited locally in the meantime.
• Restoring a backup now brings back suspend/bury state and the card identity bindings introduced in 2.6.0. Previously a restore recovered review history but not these, so restored cards could lose their suspended status and, if renamed since the backup, their link to that history.