Why does Mini not show the most likely logins first?

When I attempt to login to a site on which I have multiple logins, there seems to be no way to set the order so that the one(s) that show first are the most likely for me to use.

For example, if one out of a set of AppleIDs or Google accounts is a Favorite, it is not the one that "bubbles" to the top. Instead, it's another of the list, assumably one that sorts higher for some non-user reason.

It makes far more sense if Favorites are always sorted to the top of the lists, and that frequent ones fall into the "show if at all possible" list, as well. This is so frustrating!

1Password Version: 6.7.1
Extension Version: 4.6.4
OS Version: 10.12.5 Beta (16F67a)
Sync Type: Dropbox
Referrer: forum-search:Why does Mini not show the most likely logins first?


  • Greetings @ssh,

    The very first sort or grouping condition is how close does the FQDN (Fully Qualified Domain Name) match the website field of the Login item. If you're finding you have favourites appearing lower down the list it would indicate that the website fields for the various Login items differ to some degree. Some will be a exact match for the FQDN while others will only be a match for the registered domain. If you make the website fields consistent over the various Login items you should find that favourites always bubble to the top and that after that alphabetical ordering based on the title will determine the rest.

    If you find this isn't the case please do say.

  • sshssh Junior Member

    I don't think that's what I'm seeing, but it's hard to get back to exactly where I was. The first one has this URL:


    The favorite one has this:


    ...and the page is the Google authentication page, I think, so perhaps that's an "accounts.google.com" page?

    This kind of thing is so frustrating, and cleaning it up is very, very difficult. What's your recommendation for cleaning it up?

    FWIW, I think the favorites should always move to the top if there is a URL match like this one.

  • Hi @ssh,

    Your example does fit in with what I was referring to :smile: Googles login page is served from the FQDN accounts.google.com so when 1Password looks it considers any full match to accounts.google.com as being a primary match. It will also look for any Login items that match the registered domain name of just google.com but these are considered a lesser match even though 1Password will be happy to fill using this Login item. If all of your Google Login items have website fields that point to accounts.google.com you will find they are all treated equally and favourites will indeed appear at the top.

    If you don't use open and fill then simply storing https://accounts.google.com in all of your Google Login items would be sufficient. If you find you want certain Login items to be redirected to particular pages though you will need to go through the login process once for each one and identify the correct URL and query parameters that e.g. to proceed to your Google mailbox it would be something like https://accounts.google.com/ServiceLogin?service=mail&passive=true&rm=false&continue=https://mail.google.com/mail/&ss=1&scc=1&ltmpl=default&ltmplcache=2&emr=1&osid=1#identifier and I suspect it's the continue parameter that will influence this. This bit is just like what you might do to set up the ideal bookmark in your browser.

    Does this help at all?

  • sshssh Junior Member

    Yes. I went through and changed all my google.com logins to be google.com. I would prefer to have Favorites override URL specificity, given the crazy URLs that so many sites now use for password changing, account creation, etc. But, at least I understand how you do it at this time.

  • brentybrenty

    Team Member

    What I do is use an actual login URL for most of the sites I have saved in 1Password. This has two useful effects for me:

    1. When opening the login "cold" (not already at the site), 1Password takes me to the login page.
    2. When already at the site, 1Password will still fill the login (or offer it in a list with others for the site).

    I don't think we want Favorites to override more specific site matches, but we'll keep your feedback in mind as we develop future versions. Cheers! :)

This discussion has been closed.