I noticed this too and I was waiting for it to re-occur to make sure I wasn't imagining things
and to make some instructions how to reproduce the problem.
When it happened I noticed that the 'Password last changed' timestamp hadn't been been updated
when I last changed the password.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
PW Safe: Ver 3.51 64-bit
Environment: Win 10 Pro
This is new behavior after migrating from 3.50 to 3.51.
+++++
I use the Password Expiry feature to "flag" when it's time to change passwords based on age.
However, when an entry's password is "flagged" ... and the password changed ... the "flag" doesn't reset.
(at least not on the initial password change)
In order to clear the flag, the password must be changed TWICE.
This in 100% repeatable.
Selecting either "Apply" or "Ok" after making the initial password change does not alter the behavior.
Admittedly only a minor nuisance.
Last edit: NoVA_User 2020-02-02
I noticed this too and I was waiting for it to re-occur to make sure I wasn't imagining things
and to make some instructions how to reproduce the problem.
When it happened I noticed that the 'Password last changed' timestamp hadn't been been updated
when I last changed the password.
Rony:
Any "thoughts" on this one?
Can't reproduce this on my machine.
A ticket with a sample database and exact instructions to reproduce would be helpful.
Raised as bug #1512 with screenshots and an example safe.
Cheers
Many thanks to you both for your efforts. (details @ bug # 1512)