Preserve advanced search options
Popular easy-to-use and secure password manager
Brought to you by:
ronys
Menu
▾
▴
#795 Preserve advanced search options
I save my old entries under a group named Closed. Since the names can match those in current entries, I use the Advanced Search dialog to ignore entries in the Closed group. Unfortunately, I have to do this every time I start the application. It would be great if the advanced search options were made persistant, so the settings would be the same the next time I started the app.
Thanks!
0.96BETA under Debian GNU/Linux (jessie) as VMware guest under OSX.
I set the option to save the database immediate after edit or add, so I would be content if the database were saved when I pressed the OK button in the Advanced Find Options dialog. Perhaps the save could honor the "Save database immediate after Edit or Add" option.
I would like to second this feature request. I do a very similar thing and would love to have the feature to exclude a special Group from find/search without having to do it with advanced find/search every time I want to do a find/search. I call my group 'Z Trash' (like 'The Trash' in a foreign English accent!). I like it being the last Group in my list because of alphabetical sorting.
Fyi, from v3.36 on, PasswordSafe has a feature to export a Group as a new database. It's very handy for periodically archiving old entries that has been placed in the same Group.
This could be implemented by adding a filter to exclude entries in your Closed group (filter criteria would be "Group" "does not begin with" "Closed"). This entry can be saved in that particular database or it can be exported to an XML file (autoload_filters.xml) to be loaded at application start.
Last edit: DrK 2015-10-27
The current Advanced settings used by Find/Search, Export, Compare, Merge and Synchronise are retained during the current session (I believe that they are independent). Since these may contain information about subgroups within the database depending on the advanced setting used, we do not want to save it in the PasswordSafe configuration file.
It may be possible to add a new DB preference (i.e. stored encrypted within the database) in a future release.