Auto-Fill Errors on certain sites.

pms

Hi,

I have been seeing some consistent, some occasional auto-fill errors and wanted to log / make sure I am not doing anything wrong.

i am using Safari 8.0.3 (10600.3.18) with 1Password plugin 4.0.3.b7

The first is on the UK HRMC World Pay page (https://www.tax.service.gov.uk/pay-online/self-assessment - You need a UK GOV login to do this - so you may not be able to get to the page) - where if I auto-fill in CC then use an identity fill in - it was changing the month on the expiry (took a couple of failed login attempts to note this). Looking at my identity details can't think what would cause this as its not filling in with anything related to D.O.B. ?!

I have the source of the page (with some personal UK REF/Bill Amount removed) I can send as required.

Secondly - I have constant issues with a local takeaway delivery company https://www.deliverance.co.uk Where personal info is pre-filled (by site cookie) then if I Credit Card autofill - the Card start date is set to the same as the expiry, the contact number (mobile) field - phone number is replaced by my Credit Card number and printed on the invoice! (discovered the first time when I did not pick it up).

Once again I have the source of the page I can send

I was wondering in some cases where I should save a single CC + personal identity / address as one entry - however that becomes complicated with billing vs delivery addresses where you want it to go somewhere different....

littlebobbytables

Hi @pms

I can confirm the WorldPay behaviour but I can also give good news. We're working on a new filling logic and having just tested the latest 1Password for Mac beta with beta extension I found it filled in everything properly without overwriting. I don't know when the new filling logic will be ready for release but I can say I think you'll like it when it comes.

It's a similar situation with Deliverance. I can replicate your findings but the new filing logic does a better job. Now it still needs some refinement there as we're not filling in either the valid or expiry dates correctly but in the beta we don't replace the mobile number with your long card number, probably the worst part of your findings.

Depending on how often you use these sites you might want to consider the beta of 1Password for Mac to go along with the beta 1Password browser extension. If you are interested let us know along with what version of 1Password you're currently running either Agile Web Store (AWS) or Apple's Mac App Store (MAS).

pms

thanks for the quick response - looking forward to the new version, yes I would be interested in the beta and I have the MAS option currently.

littlebobbytables

Hi @pms

So just before you start playing with the beta there are a couple of things to be aware of.

• Jumping between the MAS and Agile Web Store (AWS) version is best kept to infrequently. The files are kept in different locations and don't remain in sync. It's easy enough to resolve but not if you want to jump between the two repeatedly in a single session.
• The beta will mean you cannot use iCloud sync because we don't have a beta for the MAS version.

So the first thing to do is quickly check and see if you've ever ran the AWS version before.

Open a Finder window and use the keyboard shortcut ⇧⌘G to open the Go to Folder... window. Paste in the following location ~/Library/Application Support/1Password 4/

If it says "The folder can't be found" in the corner of the window that's fine (see image below)

If it takes you to the folder you have either ran the diagnostic report tool or the AWS version in the past. If you move the 1Password 4 folder to your Desktop that will keep it out of the way.

Now you want to download the beta from our AgileBits Download page. To get the beta you will need to click the Enable betas link near the top, next to the ladybird image.

Due to a bug in Yosemite you might be best to now drag the 1Password application in your /Applications/ folder (the MAS one) to your Trash. The reason is a bug in Yosemite where it gets confused over which 1Password mini it should launch. Given 1Password mini exists inside our application you'd think it could get that right but it's an issue for the moment.

With no vault present the beta should pick up

1. That you have purchased the MAS version already.
2. You have a MAS vault

It will import the MAS vault, a snapshot of what it was at that point in time. If you were syncing before you will need to set that up again as the two versions are forced to keep their files in different locations.

Now you're already running the beta of the browser extension so you're good there. At this point you should be able to replicate my findings with the two sites you mentioned.

Now if you want to return to the MAS version there are a couple of things to consider. If you haven't changed your vault at all since you started playing with the beta then you can simply trash the beta application, download the MAS one again and continue where you left off. The reason you can do that is if both vaults are the same there is nothing to import from one to the other.

If you have added items or modified existing ones while you use the beta then we need to get those alterations into the MAS version. I can think of a couple of ways of doing this.

One route would be to carefully follow our Starting Over, following the part as for the MAS version. That way when you download and open the MAS one it will do what the beta did, see it doesn't have a vault but that you have one for our AWS version and import it.

If you have any questions from that relatively lengthy post or feel certain parts need expanded etc. please let me know :smile: