Beta 7.6.1.0: Why 1Password start to suggest a lot of password instead the one on my sites
Hi,
I have owe domain, with a lot of site attached:
xxxx.mysite.net
yyyy.mysite.net
zzzz.mysite.net
some accounts are favorite, some are exact match in the url part.
when I'm connecting to yyy.mysite.net he will suggest all the 15 account I have to connect to ".mysite.net" but the main one, the one tag as favorite, The one who have the url "https://xxx.mysite.net" ... is in the middle and I have to scroll, multiple time per day, to reach it...
previous version had better match there... any change who are responsible of it? any way to fix?
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided
Comments
-
Hi @mcnahum!
1Password has always showed all logins for a certain domain, even when the subdomain is different, so there has been no change there. However, 1Password should still show you Favorite items at the top of the list. I have just tested this on this forum and 1Password showed the favorite item in the first place.
I am also running version 7.6.1.BETA-0. Can you please try quitting 1Password completely (right-click on 1Password mini in the menu bar at the top right of your screen > Quit 1Password Completely), and then relaunch 1Password? Do you still see the same thing?
0 -
Thanks, it seams that a full clean put back the favorite on the top...
I'm still thinking that an exact match could do an autofill...as why not :->0 -
Perhaps 1Password could allow us to specify an entry for exact URL matching. Like @mcnahum, I run into this issue. For example: I have logins for my Banana Republic card and Verizon card, both of which are serviced by Synchrony Bank. For Banana Republic, the URL I have in 1Password is https://bananarepublic.syf.com/login, and the URL for Verizon is https://verizonvisacard.syf.com/login. Both logins show for each website.
0 -
Correct; as they are both on the same domain, they'd both be suggested. We do not intend to change that, as there are at least as many if not more cases where not doing so would cause problems. I apologize for any inconvenience caused.
Ben
0 -
First of all: Why should are favorites prioritized to "matches"? Second: What exactly qualifies as a close match? Subdomains don’t seem to be used for sorting in my case at all. It’s alphabetic order what makes e.g. "Wiki" appearing at the very end. Using numbering seems 1980 style, but I’m using this now.
0 -
First of all: Why should are favorites prioritized to "matches"?
Sorry; to clarify: items that are both a match and marked as a favorite are prioritized (as you've told us they're you're favorite items, and thus seemingly most likely to be frequently used). Items that are favorites but not matches for the current website shouldn't be suggested at all.
Second: What exactly qualifies as a close match? Subdomains don’t seem to be used for sorting in my case at all. It’s alphabetic order what makes e.g. "Wiki" appearing at the very end. Using numbering seems 1980 style, but I’m using this now.
For example, let's say you have items which have the following
website
fields:- https://1password.com
- https://my.1password.com
- https://start.1password.com/profile
- https://start.1password.com
If you are visiting https://start.1password.com/profile then the ordering of these items should be something like:
- https://start.1password.com/profile (exact match)
- https://start.1password.com (next closest match)
Then followed by
(admittedly I'm not entirely sure how these would be sorted — likely alphabetically, as you say)
Numbering could certainly help if you want to force a certain ordering, though I agree that does feel a bit old school.
Ben
0