Suggestion Do not destroy data when replacing a login

invalidptr

Like a lot of sites, Wordpress sites have a login page ([url]http://blog.example.com/wp-login.php[/url]) and a different page to change your password ([url]http://blog.example.com/wp-admin/profile.php[/url]). The 1Password UX can suffer in these cases. While I was on the Profile page to change my password I used the "Strong Password Generator" to generate the new password and clicked the Fill button. After clicking Update Profile I was prompted by 1Password to save the Login. I was hoping 1Password would update my password in the existing "Blog Example" 1Password login so instead of using the "Create new login" option I selected "Replace Blog Example". Instead I found 1Password really did replace my original "Blog Example" with one as it relates to the Profile page and had lost my Username in the process. The username 1Password grabbed from the Profile page was not the correct one. I then went to the 1Password trash and to my horror didn't find the prior login information! in hindsight I can understand what happened and why Agile is unlikely to solve this issue.



My feature request: [B]When doing a replace, the prior Login Information should be moved to the trash and the new login information created using the same name.[/B] In this way no information is lost.

Nik

Thank you for the feedback! You're right, replace really does replace the item. We have some ideas for improving this process in the future. In the meantime, we would suggest saving the login with a new name instead of choosing the replace option.