Login entry has 2 password fields and same password

teal_oak

Hi Well done for the continuing improvement in 1P 4 and 1password.com. I have a problem in that older login entries have 2 password fields and display the same password. The sites never had 2 passwords. If I delete the password from one of the fields (in the windows 10 program), predictable the field does not disappear. Is there any easy way of deleting the field ?

Also just a reminder that clicking on an alphanumeric icon still does not select the alphanumeric pick list as it does in the Windows phone version.

Thanks and bye.

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided

MikeT

Hi @teal_oak,

This is for 1Password 6 Beta, right? If yes, were these items imported or copied to your 1Password account prior to the 197d update? We made a lot of data consistency improvements, one of which is related to your issue with older Login items.

I would recommend re-copying or re-importing the same item from your current vault folder to your 1Password account and see if it is better now. If yes, you can delete the older copy.

As for the alphanumeric sorter, it's on our list to improve in a future update, we have to redo this completely.

teal_oak

102 login entries unfortunately all with duplicate password. My fault for not picking it up earlier. Now what was the password for my old opvault local file 10 weeks ago? GOK tried all the usual suspects but no joy..

Any other way of tidying this up? Export and reload into 1password 4?

teal_oak

OK now got the password and I will try and sort out.

AGAlumB

Thanks for the update! I'm sorry for the trouble, but I'm glad to hear you were able to get the password after all!

Phoeneix

Hi! I am also suffering from this issue, and was wondering if there is (or will be) another solution other than reimporting? I have hundreds of password entries, and it's been a while since I've used the old database, so reimporting would mean bringing over a lot of out of date information which would be painstaking to sort through. =( If there was a way to simply delete line items from within a password's edit screen, that would actually be less time-consuming than reimporting.

A couple of other things I have noticed regarding this issue: (1) In some cases the "duplicate" password line is the same as the first, but in some cases it is an older version of the password. (2) The Windows 6 Beta desktop app is the only one that shows these duplicate entries; neither the web version nor the Windows Store app suffer from this issue currently (which makes me hold out hope that the desktop app issue can be corrected without the need to reimport?).

Thanks!

MikeT

Hi @Phoeneix,

These aren't app issues, the desktop version of 1Password 6 Beta just happens to be the latest version that is showing more data than what the previous few-months-old Windows Store version is showing. When we update the latter version in the near future, it will show these extra fields just like the desktop version, we're actually going to bring over the same database structure in there that we've rebuilt in 1Password 6.0.197d update.

Re-importing or copying the items again from the local vault to your account is the easiest method to address all of the items at the same time but it is not required. When we add full support for the item editor to edit all fields in a future update, you may be able to address these issues but you'd be spending more time in the long run trying to fix different things that was imported incorrectly from the pervious beta builds.

We've addressed nearly all of the data inconsistency issues we found for various older vault formats from the past decade in the latest update, so that you won't deal with them later. There are a few remaining tasks we have to improve the data integrity but these tasks will not require any efforts on your part, it'll be fixed on the fly in an app update soon. We do not anticipate any more of these issues or any more of the database cleansing that we did in the 197d. This should be the last time you should need to re-import, except for any file attachments, that's a different story.

Phoeneix

Thanks for the info. Sadly, due to not knowing what I've changed and haven't since I stopped using the old database, I'm going to have to wait and eventually go with the deleting the fields method. Are there any other database problems that I should be aware of that might stem out of this?

AGAlumB

@Phoeneix: Indeed, I'm sorry for the trouble. The good news is that, apart from being patient, you're all set. We're working to iron out the rest of the performance and formatting issues, so there's nothing you'll need to do on your end except stay up to date. :)

Phoeneix

Sounds good - I can live with that for now. Thanks, Brenty!

AGAlumB

Likewise, thanks for participating in the beta! :chuffed: :+1:

Phoeneix

I just saw (and tried successfully) the latest feature that cleans up these entries when copying between vaults. Fantastic! Thanks for implementing that! =)

MikeT

On behalf of the team, you're welcome!