Autosave stopped working

tyrotex · August 2012

Khad,

Thanks for the link to the 3.9.4 Safari extension. I had already tried reverting the main app to 3.9.5 (no effect), but had no access to older extensions.

Unfortunately, the 3.9.4 Safari extension had no effect, even with all other extensions disabled.

Regards,

John

PS: I should add that installing the 3.9.4 extension caused Safari to lock up, i.e. no response to any navigation; the Downloads list (from which I had double-clicked the downloaded extension) was locked open. I had to force quit Safari. On the first restart of Safari, the extension showed "Problem with Database" message when I entered my password in the extension. Another restart led to everything working OK, except (of course) AutoSave prompting.

tyrotex · August 2012

Hi Khad,

Some more info for you. Good news for me; Not so much for you, though :-}

It seems that autosave IS working. If I go to a brand new site and enter some login info, I DO get prompted to autosave.

BUT, it seems that, on some websites, if I dismiss the 1P autosave bar (by clicking the "x"), 1P no longer prompts to autosave. It seems that tumblr.com is one of those websites. On other websites, like paypal.com, 1P continues to prompt for autosave, even after dismissing the autosave bar.

- I have updated the extension to 3.9.5

- I have all my other extensions and plug-ins enabled

- Autosave works whether I'm using a local or Dropbox keychain

- Both Safari and Chrome show the same behaviour.

It would seem that the problems that I (and possibly George) have been reporting is due to the fact that we were continually using tumblr.com as the test site.

So, for me, everything seems to be working, with the exception of that weirdness on some websites. All I can do is apologise for pointing you in the wrong direction, although I guess anyone involved in front-line support must be used to that!

Unfortunately, it means that your team now has to chase down why autosave stops working after the first dismissal on some websites, but not all.

HTH,

John

PS: This time, I did not get a lockup of Safari when I installed the 3.9.5 extension

bungle · August 2012

Sorry for the slow reply!

I too did not have tumblr.com as a 'not to autosave'.

Moving the extensions appeared to work for me for the first test on tumblr. I tried on tumblr and it worked, I then crossed the autosave bar, closed the tab and tried tumblr again and I did not get prompted to save.

I have just tried another few sites and I have not been prompted since. Is it possible that after dismissing the autosave bar once it refused to show again?

The older 1password extension would not open for me from the downloads in safari.

Cheers,

George.

EDIT: I have just tried 1Password in Chrome and it works perfectly, I can try jibberish on a site, close the prompt, try jibberish again and it will again prompt to save. I then tried other sites and it was perfect.

I have a tweak to Safari called Glims, I have just thought, do you think this could cause issues?

khad · August 2012

Thanks for the updates, guys. The issue definitely seems to be only in Safari and it sounds like 3.9.4 does not help. I don't think Glims is the issue since John does not also have it installed, but Glims would have been removed when you followed the steps in my post above about [url="http://forum.agilebits.com/index.php?/topic/10583-autosave-stopped-working/page__view__findpost__p__61276"]removing Internet Plug-Ins[/url]. Try removing Glims files from both of these folders just to be sure:

[CODE]/Library/Internet Plug-Ins

/Library/ScriptingAdditions[/CODE]

It sounds like the specific URL has some effect as well as repeated prompts after an initial dismissal. Do you get the prompt again if you restart your Mac or is it gone forever if you dismiss the autosave bar on a certain URL?

Another thing I just discovered is that there is a problem with autosave in [b]fullscreen[/b] mode. Please be sure you are testing in a regular Safari window not in fullscreen mode or you will not see the autosave prompt.

tyrotex · August 2012

First off, apologies for the length of this post.

In answer to your questions, Khad, certain URLs (like tumblr.com) are NEVER prompted for (both in Safari and Chrome).

I've been testing again today in a window rather than fullscreen which is how I normally use Safari.

The behaviour survives restarts of the browser(s) and machine.

In case 1P was caching the exclusion of tumblr.com, I've been experimenting with deleting 1P cache files such as:

~/Library/Containers/com.agilebits.onepassword-osx-helper/Data/Library/Caches/1Password & 1Password.cache

/private/var/folders/5p/ndr3stp97bl5r7drz293c58m0000gp/C/com.agilebits.onepassword-osx-helper

I also found two copies of ~/Library/Caches/com.apple.Safari/Extensions/1Password.safariextension. I think this came from some of the Safari freezes during extension installation that I've mentioned. I deleted the oldest copy.

These changes had no effect. Caches seem to have been recreated OK.

Unfortunately, I just cannot get an autosave prompt on tumblr.com. Autosave DOES prompt on other sites I have tested. I haven't tested exhaustively, but at the moment, tumblr seems to be just about the only site I cannot get an autosave prompt.

The login page for www.winemarket.com.au (which redirects to [url="https://checkout.netsuite.com/s.nl?c=875702&n=1&sc=1&category=loginregister&it=A&login=T"]https://checkout.net...er&it=A&login=T[/url]) also dos not prompt, but I think that is because it is a flash-based login which doesn't work at all for me unless I give ClickToPlugin an exception. Just now, I have tried a jibberish login to vimeo.com. I was under the impression that they use a flash-based login also. However, autosave worked fine.

While I was doing this testing, I found something rather strange, which may be an artefact of the messing about that I did with the caches above. I hope it is not another confusing red-herring, and I apologise in advance if that is so.

What I found was that there seems to be an interaction between the ClickToPlugin and the 1P extensions.

After a period of 1P working fine (except for tumblr) over Safari restarts, etc., I looked at ClicktoPlugin's preferences which is presented as a page in Safari. I made no changes and dismissed the page (cmd-W). 1P seemed to still work fine.

If I then restart Safari, 1P extension icon looks normal on the address bar, but is logged out. 1P Autosave or "Enter master password" prompts do NOT appear on websites where it used to work.

I click on the 1P icon and enter my password. A small red "1" appears on the 1P icon and the red "Problem with database" message in the login screen.

If I restart Safari normally, I get the same behaviour, i.e. icon looks normal, but 1P login fails with database error.

However, if I close Safari with the suggested Cmd-Opt-Q and restart, everything starts working - login, autosave (except for tumblr) etc.

So, in some way, it seems that just opening ClickToPlugin's preferences does something to mess up 1P extension's database connection, but without obvious warning signs (the red flag doesn't appear on the 1P icon until after a 1P login attempt). Logically enough, without the database connection, 1P will not prompt for anything.

I hasten to add that, until today, I have not been opening C2P's preferences at all during my previous testing; just disabling it with the other non-1P extensions.

In case all of my testing has made 1P itself unstable, is there any way I can wipe my 1P installation completely and start from scratch?

Obviously, I don't want to lose my (rather large) database/keychain, although I do have 1P and Time Machine backups, not to mention Dropbox copies. AppCleaner show that it will delete 11 objects (files and directories). Will that remove everything or will some odd cache/directory/plist be left to confuse a future installation?

EDIT: ClickToPlugin extension version is 2.7

bungle · August 2012

[quote name='khad' timestamp='1344390136' post='61324']

Another thing I just discovered is that there is a problem with autosave in [b]fullscreen[/b] mode. Please be sure you are testing in a regular Safari window not in fullscreen mode or you will not see the autosave prompt.

[/quote]

I always use fullscreen, and yes working in window mode works flawlessly for me, thanks for identifying that! I can live with making another desktop and using Safari maximized until you can find a fix I think!

Thanks again for the help! If you need me to test anything else just let me know!!

khad · August 2012

Awesome! Thanks for letting me know that was the issue for you, George. We only [b]just[/b] identified the problem in fullscreen mode. That will be one of the [i]first things[/i] we check now if anyone else reports autosave problems until we get that resolved. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/smile.png' class='bbc_emoticon' alt=':)' />

John, is it safe to say that autosave is [i]generally working[/i] for you except on tumblr.com? This is perplexing, but does help us track the issue since it is not completely broken. There are things that certain sites can do to prevent autosave, but in general it should be working on the vast majority of sites.

We'll try to do some testing with ClickToPlugin to see if we can reproduce anything. Can you confirm for me that autosave is working well without ClickToPlugin installed? You may have said that, but it was tricky following everything in your post. It's been a long day for me. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/laugh.png' class='bbc_emoticon' alt=':lol:' />

tyrotex · August 2012

Sorry to deluge you with all that stuff :-}

Yes, autosave seems to work for me everywhere except tumblr & some other sites with weird login setups.

!P works fine with ClickToPlugin UNLESS I open C2P's preferences. If I do that, 1P extension is borked until I reset Safari with cmd-opt-Q.

So, basically 1P is fine. I can work around these few wrinkles. I just wanted to bring them to your attention in case you can reproduce them and improve 1P.

Regards,

John

khad · August 2012

I'm not able to reproduce any trouble with ClickToPlugin (specifically when opening its preferences), and I'm still a bit perplexed as to why autosave would not be working for you on Tumblr's login page. We'll continue to monitor the situation. You can be sure I'll post back here with any additional information we uncover.

Thanks so much for all your help with this thus far.

Cheers!

tyrotex · August 2012

I'm glad that the ClickToPlugin issue is limited to me and not a general problem. Hopefully the other issues I've seen are similarly idiosyncratic. Thanks for checking it all out and my apologies if I've been leading you on a wild goose chase.

I think it might be time for a fresh install of everything! I'll give 10.8 a go and see what happens :-}

Regards,

John

khad · August 2012

I'd love to know if that changes anything for you.

tyrotex · August 2012

Hi Khad,

Well, I've done a clean install (not upgrade) to 10.8.

The ClickToPlugin problem I noted earlier is no longer a problem. Google Chrome seems to work OK. 1P does not prompt for autosave at tumblr.com with either Chrome or Safari.

Safari 6 is another matter however.

First off, I experienced the Safari freeze I described when I double click on the downloaded 1P extension as per the instructions. But, I had the same problem with another extension also, so it may not be specific to 1P.

Autosave prompting is a bit hit and miss. Sometimes it works fine; Others not.

I have been using dropbox.com login to test a gibberish login. I can get 1P to prompt for autosave IF the extension is logged out. It will prompt for the master password, then to save the site. Good!

However, If the extension is logged in when I enter gibberish login details, 1P does not prompt to save. Also, after the failure of the autosave prompt, the '+' button in 1P does nothing. It is as if 1P does not respond until after the website has successfully completed the login.

OTOH, the '+" key DOES work to save login details if I use it BEFORE pressing the site's login button, but not after a failed login.

In case the strange behaviour was related to the gibberish credentials, I filled the login fields with a valid login but changed the password detail. This is attempting to mimic logging into dropbox after changing the password. I get the same behaviour ('+ works before pressing the "Login" button, but not after a failed login attempt; there is no prompt to autosave the new credentials).

I hope I have described that use case sufficiently clearly for you to try it out.

If the behaviour of 1P has been changed to only save after a successful login, I can see that would be very useful in preventing the database filling up with invalid information. But it means that 1P cannot be tested with gibberish credentials as we have been doing so far.

Regards,

John

Autosave stopped working

Comments