[codex] Document KeePass plugin cache recovery#156
Draft
SirAndrosBot wants to merge 1 commit into
Draft
Conversation
SirAndrosBot
force-pushed
the
codex/issue-110-keepass-257
branch
from
1f00670 to
e486c48
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Added a short installation troubleshooting note explaining how to clear KeePass's plugin cache and fully restart KeePass when KeePassWinHello disappears from
Tools>Pluginsafter a KeePass upgrade.The instructions use the actual KeePass UI: open
Tools>Plugins, clickClearunderPlugin Cache, fully exit KeePass including its tray icon, and restart it.Why
Issue #110 initially looked like a KeePass 2.57/2.57.1 compatibility regression, but multiple users confirmed KeePassWinHello 3.3.1 works on those versions. One affected installation recovered after clearing KeePass's plugin cache and completely restarting KeePass.
The evidence points to stale KeePass plugin-cache state rather than an incompatible KeePassWinHello binary. Because KeePassWinHello code cannot run when KeePass does not load the plugin, runtime handling cannot reach this failure mode. Documenting the proven host-level recovery is the smallest honest fix and avoids encouraging an unnecessary downgrade to 3.2.
User impact
Users who lose the plugin after a KeePass upgrade now have the recovery steps next to the installation instructions. The Plugins dialog and its cache controls are provided by KeePass, so the recovery remains available when KeePassWinHello itself is not loaded.
The minimized-window behavior discussed later in #110 is separate issue #107 and is addressed by PR #141; this PR does not mix that runtime behavior into the cache-loading fix.
Review and validation
Clearbutton under thePlugin Cachesection and that the dialog remains reachable when this plugin is absent.git diff --checkorigin/master.How to Install.No build was run because this changes documentation only. The cache failure was not reproduced locally; the recovery sequence is based on the successful confirmation in #110. The exact control label was independently checked against KeePass 2.61.1; the issue discussion describes the equivalent cache clearing flow on KeePass 2.57/2.57.1.
Closes #110