'Go & fill' high maintenance? login URLs changing...

Stonecurse

Hi, Just wanted to get some feedback on what you think about keeping all your logins Go & Fill data up-to-date, and working.

First, I never really use Go & Fill. But I recently was updating my 1PW db and thought, might as well go all the way. After updating most of my accounts to work again with Go & Fill (new login URLs/web form details), I started to wonder why I'm even spending the time.

Is there something I'm missing here, or should I just set the website URL to e.g. 'https://www.amazon.com' and be done with it? Then just go to Amazon login page and press CMD+.

Thanks and please be nice, I'm not trying to be negative at all. The Go & Fill feature works great and I understand how to some it could be essential to their workflow!

littlebobbytables

Hi @Stonecurse,

So there are a couple of different routes to filling as you're aware. There is the keyboard shortcut ⌘\ which is titled Fill Login on current web page and domain matching works here. Now if you have a Login item with the exact URL for the login page it will favour that over one with just the domain. Still, if you have an Amazon Login item with https://www.amazon.com as the website field and you visit their login page it will work.

Now open and fill will open the URL you have stored and attempt to log in on that page. Here's where storing the exact URL makes the difference. If the URL doesn't take us to a page where you can log in then trying to submit your login credentials will fail.

It all really comes down to a preference really. If you like the idea of open and fill and find it useful then you'll want to ensure the full URL is stored. If you find opening the login page first simply fits in better with your personal workflow then what you're doing is fine too. If you ever use our automated system for saving Login items or indeed our Saving a Login Manually guide then the full URL is stored as a matter of course.

It's really what works best for you though.