Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KeeAnywhere Offline Cache path #148

Closed
gb-velir opened this issue Oct 4, 2018 · 3 comments
Closed

KeeAnywhere Offline Cache path #148

gb-velir opened this issue Oct 4, 2018 · 3 comments
Labels
Milestone

Comments

@gb-velir
Copy link

gb-velir commented Oct 4, 2018

Environment:
Windows 10 v1809
KeePass 2.4.0 (installed)
KeeAnywhere plugin 1.5.0 stored in %PROGRAMFILES(x86)%\KeePass Password Safe 2\plugins

I am expecting the cache according to release notes to be %APPDATA%\KeePass but instead it's %PROGRAMFILES(x86)%\KeePass Password Safe 2\

2018-10-04 14_18_22-window

@Kyrodan
Copy link
Owner

Kyrodan commented Oct 19, 2018

Maybe I have to improve identification of portable installations.
In your case it seems, that the installed version is determined as portable.
Currently it is portable, if "PreferUserConfiguration" is false. KeePass' installer has a config set this flag to true.

So please checkt the content of your KeePass.config.xml in Program Folder:

<?xml version="1.0" encoding="utf-8"?>
<Configuration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
	<Meta>
		<PreferUserConfiguration>true</PreferUserConfiguration>
	</Meta>
</Configuration>

@Kyrodan Kyrodan added this to the 1.5.1 milestone Oct 19, 2018
@Kyrodan
Copy link
Owner

Kyrodan commented Oct 19, 2018

Determination of portability starting with version 1.5.1 will be:

  • Check Parameter "PreferUserConfiguration": yes = non-portable (only check in version 1.5.0)
  • if PreferUserConfiguration is false (Config file is beside KeePass.exe): check, whether KeePass is started from ProgramX86- or Program-Folder => if yes: non-portable

@gb-velir
Copy link
Author

That was indeed the case, because originally the setup was portable, then I switched to installed. However switching to

<PreferUserConfiguration>true</PreferUserConfiguration>

did not fix the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants