#1269 Can't store filter that uses policyname in database

[Mitch Ames]

Create a new database with some entries, including an alias and a named policy ("not changeable").
(Save as 1.psafe3, and make a copy as 1-original.psafe3)
View -> Filters -> Manage
Create a new Filter ("Filter 1")- Entry type is not an alias entry AND Password Policy Name does not equal "not changeable"
The filter works as expected as a Session filter, so:
1 - Copy to DB
2 - Export (to 1.filters.xml)
Save the database (with the filters)
Close Password Safe
Start Password Safe and open the database - it says "Trouble reading stored filters (version mismatch?). Filters will be unusable."

Roll back to the previous version of the databse that did not have the filters (1-original.psafe3), and open it.
View -> Filters -> Manage
Import 1.filters.xml

It says:

File: 1.filters.xml failed validation against XML Schema:

Error (80004005): line 25 character 15 Element 'policyname' is unexpected according to content model of parent element 'filter_entry'.
Expecting: group, grouptitle, title, user, notes, password, create_time, password_modified_time, last_access_time, expiry_time, record_....

(I'm assuming that these two items - storing the filter in the database and importing the xml - are related.)

The problem appears to be related to the use of Password Policy Name. If I repeat the whole thing using a filter of
Entry type is not an alias entry AND username does not equal "b"
instead, both saving an importing work fine.

Attached are:
1-original.psafe3 = the database before an filters were created
1.filters.xml = the exported filters
1-stored-filters.psafe3 = the database after I created the filters, copied them to the DB and saved it
Database password is 1234

[DrK]

Original post deleted as new solution devised.

[Rony Shapiro]

Thanks for the accurate description and files!
Fixed (by DrK) in commit 8fe4cbc.
Let me know if you'd like to test the fix, and I'll upload a pre-release build.

[Mitch Ames]

Yes, I'd like to test the fix / pre-release.

[MrMe]

Maybe this issue I noticed can be fixed at the same time? I was trying to follow the problem description of this post, so I dowloaded the files. I didn't see the 'Entry type' as one of the options in the 'Click here to pick a field' column. After a couple of attempts, I figured out what the issue is. On the windows 8.1 laptop with a 1366x768 screen resolution that I was using, when the user clicks on the 'Click here to pick a field' on the 'Set display filter' window, you can definetly see all the options (with 'Group' at the top and 'Unknown fields' at the bottom) if you move the 'Set Display Filter' window to th top of the screen or to the bottom of the screen. I think what is happening is that the drop down box can't fit all the options when the there is not enough vertical display height to work with. The current drop down box either displays the options above or below the 'Click here to pick a field' button, so some of the options get cutoff if the 'Set display window' is not in the right position for all options can be seen.

[DrK]

I do have a fix for this but please raise a new Bug Report - something along the lines of can't see filter field in dropdown list if too big for the screen resolution. I'll leave the exact wording to you.

We prefer a single issue per Bug Report as it makes tracking easier.

Thank you

[Rony Shapiro]

Thanks - you can try the build here.
Please let me know how it goes.

[MrMe]

Okay....I will create a new/separate bug report for the filter fields dropdown list getting cutoff on low resolution screens.

[Mitch Ames]

Version 3, 36, 1, g8fe4cbc seems to have fixed the problem.
Thanks