Ok, so to make the log access a bit easier could you instead post it on https://gist.github.com/ (no registration required)
Otherwise, could you fetch us a log from background.js? We're specifically interested in what happens during loading of the extensions, so if you can open the background inspector, then press "Reload" in chrome://extensions under Zotero Connector and paste the resulting log in the background inspector as a gist on github, that would be great.
If you type localStorage['translatorMetadata'] = {} into the the console tab in the background inspect developer tools, then reload the extension, does it start working?
Ignore the ERR_CONNECTION_REFUSED errors for the moment. Are preferences more functional now? E.g. being able to submit Report ID, status correctly shown, etc.
Sorry this is taking a while, but it seems that we're nearly there.
Ok, just to make sure you got it right, you should type localStorage['translatorMetadata'] = {} in the developer tools window that you get after pressing inspect views: background page (not in the F12 developer tools on any page, that's different). Then reload the extension and try again. You can also give us another copy of the background page log after typing this in and reloading.
This is the chrome extensions page background page inspection output generated by reloading the zotero connector (option from page right click menu), typing , navigating to the options page and clicking 'Update status' from the general tab on Connector preferences page. (hope that's right and also clear!)
Sorry, I had to go afk for a bit. So this seems all right, the log includes you typing that, but you should have typed it and then reloaded the extension (or restarted the browser), to see the effect. If Zotero client is open you still shouldn't be getting those ERR_CONNECTION_REFUSED errors, but it seems that there are bigger problems than that at the moment -- the ones we are trying to fix with that line in the console.
Could you restart the browser and check if you can at least submit a Report ID? If not, we'll push out a potential fix anyway and see if that improves anything.
The output I sent included me reloading. The second section of ERR_CONNECTION_REFUSED after the localStorage statement is what comes up when I reload and also when I refresh the extensions page. That's all that comes up
I think I have a fix for at least some of the problems you are seeing and we'll try to push it in the next couple of days.
Could you report if: 1. The connector works properly (or at least you can submit a Report ID) in a new Chrome Profile? 2. In the Preferences page you only have a "General" and "Advanced" tab, but no "Proxies" tab?
Right. In the old profile, opening the extension background inspect tools and typing localStorage.clear(), then reloading the extension should do the trick (although the previous suggestion should have done too, so maybe there's something else to the issue). Otherwise, we'll release a fix soon.
Upgrade Storage
Otherwise, could you fetch us a log from background.js? We're specifically interested in what happens during loading of the extensions, so if you can open the background inspector, then press "Reload" in chrome://extensions under Zotero Connector and paste the resulting log in the background inspector as a gist on github, that would be great.
localStorage['translatorMetadata'] = {}into the the console tab in the background inspect developer tools, then reload the extension, does it start working?Ok, just to make sure you got it right, you should type
localStorage['translatorMetadata'] = {}in the developer tools window that you get after pressing inspect views: background page (not in the F12 developer tools on any page, that's different). Then reload the extension and try again. You can also give us another copy of the background page log after typing this in and reloading.https://gist.github.com/anonymous/77b1db0bb3a51b9c22f6b30e2d58c3ed
Could you restart the browser and check if you can at least submit a Report ID? If not, we'll push out a potential fix anyway and see if that improves anything.
Could you report if:
1. The connector works properly (or at least you can submit a Report ID) in a new Chrome Profile?
2. In the Preferences page you only have a "General" and "Advanced" tab, but no "Proxies" tab?
localStorage.clear(), then reloading the extension should do the trick (although the previous suggestion should have done too, so maybe there's something else to the issue). Otherwise, we'll release a fix soon.