Mint.com Open and Fill Not working

mdvzo
mdvzo
Community Member
edited October 2015 in 1Password in the Browser

Was this ever rectified - https://discussions.agilebits.com/discussion/comment/191684#Comment_191684

I only have trouble with this site and maybe one or two others. Autofill works but not if I launch it from 1Password Open and Fill

Comes up blank all the time and yes I use https://wwws.mint.com/login.event

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

Comments

  • AGAlumB
    AGAlumB
    1Password Alumni
    edited October 2015

    @mdvzo: If you manually save a new login, it will give 1Password current information about the form and fill just fine. Just follow these steps:

    1. Navigate to the website: https://wwws.mint.com/login.event
    2. Enter your login credentials
    3. Click the 'keyhole' icon to bring up the extension
    4. Click the 'gear' icon for Settings
    5. Click Save New Login
    6. Give it a name and Save
    7. Close the webpage and select your new login from the extension to have 1Password Go & Fill
    8. Submit the form manually if you have autosumbit disabled

    However, 1Password cannot fill as the page is loading its own scripts, so you'll need to press ⌘ \ to login.

    I hope this helps. Please let me know how it turns out! :)

  • mdvzo
    mdvzo
    Community Member
    edited October 2015

    Thx I already have a Login entry for Mint.com that I created but it does not work with "Open and Fill" or if I create a bookmark from 1Password and save it in Alfred which is what I really want to do. I am forced like you say to use CMD \ to login and want to avoid this like I do with all other website.

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    Hi @mdvzo,

    So it seems it was working (we fixed whatever the issue was) and then we promptly broke it again. So it doesn't work for me with the 1Password Safari Extension in both the stable version (4.4.4) or the current betas which will eventually be version 4.5 but when I loaded up the older 4.2.0 version it does. So we've changed something and didn't realise the implications. I've re-opened the bug report with this information so thank you for reporting it. It might seem like we never worked but it did for a while (I promise) which is why we won't have been looking at the bug report recently.

    ref: OPX-260

This discussion has been closed.