Hello.
I apologize, I don't know where I should create this post, on the development forum or on the support forum, so I'm writing here. I apologize if I made a mistake, please explain if I am wrong.
The problem is this: when updating the portable version of KeePass Pro, important files (and folders) are deleted from the folder where the keepass.exe file is located. Specifically: the plugin files KeepassCommander and KPScript, a couple of other custom scripts that only work from this folder, and also the Scripts and Macros folders disappear. This is definitely the wrong approach. It would be easier for me to manually update the portable version of KeePass Pro from the developer's website than to use PortableApps, after which I need to restore the working files from a backup. These are scripts and script plugins that must work from the folder where the KeePass executable file is located.
Thank you for your understanding, sincerely.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
What are the exact folders that need to be preserved. Currently, Plugins and PluginCache are preserved. I was unaware of any additional folders and haven't use the plugins you mentioned as they aren't of use to me.
Sometimes, the impossible can become possible, if you're awesome!
Thank you for drawing attention to this problem and for your response.
I don't quite understand what you are talking about. The issue is not about needing to add any folders, but about not deleting existing files and folders, even if you don't include them in your build. Regarding the plugins I mentioned, specifically KPScript, it automates some network processes for me, and this plugin's page is featured on the KeePass website itself, not somewhere on a third-party GitHub. This KPScript plugin, like the KeePassCommander plugin, and the Scripts folder, must be in the folder with the KeePass.exe executable, otherwise they don't work. That is, they are located in the folder ..\PortableApps\KeePassProPortable\App\KeePassPro
If I manually download the portable version of KeePass Pro from the developer's website, I can easily unpack the contents of the archive into the current folder, overwriting files and folders, without worrying that files and folders not present in the zip archive will be deleted. Why can't the same be done with the PortableApps version? Does it mean that your build first deletes the contents of the folder at KeePassProPortable\App\KeePassPro, and then it is populated with the updated content? But why? Why can't you simply implement an overwrite of old files? In any case, plugins are updated with a separate tool; they don't need to be included in the build at all. Simply do not delete existing files that are not part of the PortableApps KeePassProPortable build itself.
I hope I have explained my point of view in sufficient detail and clearly.
This is now fixed with 2.61 Rev 2. Future updates will also preserve all files within the App directory.
Generally, the whole App directory is removed on upgrades except specific folders for things like plugins. It looks like officially promoted plugins and add-ons for KeePass Pro don't respect that kinda of structure and put their files all over the place. So, I'll have to manually WinMerge each release to the release before and manually set removed files to be removed by the launcher for each release.
Sometimes, the impossible can become possible, if you're awesome!
Wow! But that must be really inconvenient for you. It seems like the core components of the official build don't change much from version to version. If I'm not mistaken, even when transitioning to the new kdbx file format after KeePass Pro version 2.34, their composition didn't change. Back then, I didn't even immediately notice that something had changed in the database architecture itself. I used to use the setup version, but later I needed a portable version for a USB drive, and I started downloading the ready-made solution from the official site and simply overwrote the old folder when updating. I still update plugins with a third-party tool in just a couple of clicks, but you can't update the portable build that simply, which is why I switched to the PortableApps build.
In any case, thank you for your project, for your efforts, and for your contribution to the distribution of portable software.