Unsupported SIMBL plugins can cause many issues

cbmackay

I'm having a lot of trouble with 1Password's browser extension under Lion. It's basically useless.[list]

[*]it's not prompting me to save new logins.

[*]it's sometimes bringing up the pop-up rendered full of gibberish (two or three screens of info overlaid on top of each other; meaningless gibberish. Not purely cosmetic, either: checkboxes seem to work, but most other controls, including the text field, are inert)

[*]for lots of sites, including popular ones, like Flickr.com, command-\ does nothing.

[*]sometimes, when command-\ does bring up the 1Password window, I can't interact with it. Mouse, tab key: nothing. Other times it's pre-populated with bullets (clipboard contents?)

[/list]

Honestly, the amount of extra work this is imposing is getting to be a real problem. Re-saving hundreds of logins, while irritating, is understandable. I realize Apple pulled the rug out from under you guys at the last minute, but while I was grudgingly willing to do that if I had to, one at a time, as they came up during normal use, I can't do that if the plug-in isn't going to prompt me to save logins.





At this point, there's no point to the browser extension at all. I'm just using the Mac app as an encrypted DB and manually copy/pasting everything to Safari. PITA.



What's coming? Is basic functionality going to be restored? Is email support coming back? I don't like griping on a public forum like this; it's bad form. But we have no other choice. I've put off posting this in hopes of things getting ironed-out, but patience begins to wear thin.

dmkflyer

Very similar problem with Snow Leopard running latest automatically downloaded Safari extension. See attached screenshot of the new 1Password menu in Safari. Come on Agile!!!

cbmackay

Ok, I give up: how do you attach an image to this board?

cbmackay

[img]http://tantramar.ca/Safari1PasswordExtension3.7.b16.png[/img]



I give up; just uploaded it to my webserver, pasted in its url.

cbmackay

I don't get this every time, but a lot. Pretty messed-up, no? This hasn't been limited to beta releases, either.

Ben

The broken 1Password window can be caused by several unsupported Safari extensions. Because of the unsupported nature in which they interact with applications, these extensions can interfere greatly with the proper behavior of the 1Password browser extensions.



Examples of extensions we've seen that cause issues are "SafariSniffer" and "Wondershare AllMyTube/Free YouTube Downloader". It is likely other unsupported extensions would result in similar problems.



You can see if you have any of these installed by looking in these folders:



~/Library/ScriptingAdditions (in your Home folder)

/Library/ScriptingAdditions (in the root of your hard disk)



The most popular one is SIMBL, but there are others as well. Try moving anything you find in these folders somewhere else, for example, to your Desktop.



Once the files are moved, please restart Safari and I suspect you will be greeted with a much more enjoyable 1Password experience.

cbmackay

Thanks, Ben. This seems to have helped, though I did still get prompted to Command-Option-Q to clear Safari's extension database, which wiped out all the open windows (which is fine). I'll follow-up here if I have further issues.

khad

Thanks for the update, cbmackey. I'm glad things are working properly now that you have removed the unsupported plugin(s). Please let us know if there is anything else we can help with.



Cheers,

cbmackay

It is vastly improved. I wouldn't say it's working properly yet, though.



About half the time (wildly unscientific guesstimate) 1PW Safari extension fails to prompt me to save new logins. Sometimes the save pane disappears before I get a chance to use or dismiss it.



Still feeling a bit flaky.

[Deleted User]

Autosave is one of the areas we still need to work on, we really want to give you the best experience and ideally we'd like autosave to work 100% of the time, but sometimes a site will have code that just makes this impossible. In those cases the best option is to save a Login manually like so:

[list=1]

[*]Enter your username and password, but DO NOT submit the form.

[*]Click the 1Password button in your browser's toolbar, and select the "+" button in the upper right hand corner.

[*]Change the title and make any notes (if desired).

[*]Click the Save button in the upper right hand corner.

[/list]

That should work for pretty every site, unless there's something really nasty in the code.

cbmackay

Thanks, Stu.



I'll keep that workaround in mind.



Sadly, this is happening on WordPess (3.1.x) sites' admin pages, so not an obscure outlier.



Chris

[Deleted User]

I'd agree, that'd be a fairly major issue.



Here's the strange thing, I just tried some fake details on one of my WordPress installs and 1Password did prompt me to save the details for that login. We did update to WordPress 3.2.x though, but I'm not sure they made a huge change to the admin login with this. Here's our admin page if you want to give it a try:



http://impodcast.tv/wordpress/wp-login.php

cbmackay

I'm also having issues with web realms that produce a system-level login sheet under Lion: invoking the browser extension with Command-\ brings up the 1Password form, but I can't interact with it; typing goes into the sheet's username field, as does pasting. Clicking on the 1Password password field does nothing to bring it to focus. So then I'm back to manually copy/pasting from the 1Password desktop app. Sigh.



Re: WordPress saving credentials prompt: sometimes it happens, others it doesn't. These are all on my server, so same WP version.



This must be as frustrating for you as it is for me.



I also notice that this thread got a new name. Interesting.

cbmackay

@Khad: it's "Mackay", not "Mackey". Thanks. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/smile.png' class='bbc_emoticon' alt=':)' />

[Deleted User]

[quote name='cbmackay' timestamp='1313428756' post='39393']

I'm also having issues with web realms that produce a system-level login sheet under Lion[/quote]



These are known as HTTP Authentication prompts, and sadly they're not accesible to us via Safari's extensions APIs, though we are looking into some ideas to support these in the future.



[quote]Re: WordPress saving credentials prompt: sometimes it happens, others it doesn't. These are all on my server, so same WP version.[/quote]



Are you by any chance using the same login credentials for each site? I wonder if 1Password is refusing to save them because it sees a match already.



[quote]This must be as frustrating for you as it is for me.[/quote]



More exciting, we love challenges here and the transition to the new extension has been a lot of fun with a lot of hard work mixed in. This is going to set us up for years to come, in terms of browser integration at least.



[quote]I also notice that this thread got a new name. Interesting.[/quote]



We do this from time to time just to make the forums a bit more tidy, we treat this place like our home in many ways.

Ben

Hi there,



We're aware of the issue with HTTP authentication prompts. There is no API for these in Safari 5.1. We're looking for another way we can interact with them but not having an official API is the cause of the delay in getting them working.



http://help.agilebits.com/1Password3/http_auth.html



Ben

cbmackay

[quote name='stu' timestamp='1313429372' post='39396']

Are you by any chance using the same login credentials for each site? I wonder if 1Password is refusing to save them because it sees a match already.



[...]



We do this from time to time just to make the forums a bit more tidy, we treat this place like our home in many ways.

[/quote]



No, I don't use the same credentials from site-to-site. That's why I use 1Password! <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/wink.png' class='bbc_emoticon' alt=';)' />



Renaming threads? Seems a bit like inviting guests over then re-dressing them cause you don't think the other guests will like their suit. I don't recall exactly what I'd called it, but it wasn't derogatory or derisive. [edited to add missing word "think" -cbm]

Ben

Hey cbm,



No offense intended. It's common practice on these forums to rename thread titles such that they are (hopefully) more easily found by others with the same or similar issues to (again, hopefully) keep the number of duplicate threads down.



Ben