Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firefox Developer Edition disabling unsigned extensions #39

Open
markabbott opened this issue Aug 10, 2015 · 20 comments
Open

Firefox Developer Edition disabling unsigned extensions #39

markabbott opened this issue Aug 10, 2015 · 20 comments

Comments

@markabbott
Copy link

Using Firefox Developer Edition 41.0a2 (2015-08-10), which now disables unsigned extensions, including LiveReload 2.1.0.

Can the extension be signed?

@thevasya
Copy link

It's possible to allow installing unsigned extensions by setting xpinstall.signatures.required to true in about:config. This works for FF 41, but probably won't work for FF 42.

https://wiki.mozilla.org/Addons/Extension_Signing

@markabbott
Copy link
Author

OK, thanks. A reprieve for now. Will still be nice to know if the extension will get signed at some point soon.

@wmcmillian-coalmarch
Copy link

FF dev edition is now at version 42. Would love to know when this is happening.

@dwt
Copy link

dwt commented Sep 16, 2015

+1

Dear developer, could you please give an update on what you plan for signing?

@thevasya
Copy link

There's a version 2.1.1 of the LiveReload extension which is currently awaiting review.

And it seems the process is very slow: https://twitter.com/livereload/status/633191290440708096

@genxstylez
Copy link

just installed 2.1.0 on firefox dev 43. with xpinstall.signatures.required => false

@jnachtigall
Copy link

Seems like the current version (2.1.1) is already at AMO. So I think this issue could be closed.

@markabbott
Copy link
Author

v2.1.1 from addons.mozilla.org doesn't seem to work yet, though.

@jnachtigall
Copy link

@markabbott Works perfectly for me. Maybe you installed a previous LiveReload xpi directly/manually (when there was no current version at AMO). In this case you must deinstall the manually added one, and then reinstall the one from AMO

@jnachtigall
Copy link

@markabbott Which OS are you on? Works perfect on Windows for me, but does nothing on Ubuntu. Maybe related to #6

@markabbott
Copy link
Author

@jnachtigall Ah, it does work now. I suspect I hadn't properly uninstalled the previous version and restarted the browser properly.

It's also confusing that the AMO page still says that the extension is deprecated. But it's nice to not have the security warnings now.

@jnachtigall
Copy link

@markabbott Glad it works now. Still which OS are you on? ;-) (I could not get it working on Linux)

@markabbott
Copy link
Author

@jnachtigall Sorry, I'm on OS X, mostly. I use a Linux box occasionally, so I'll try that later.

@fredrikekelund
Copy link

2.1.1 is broken for me as well (FF43 on Fedora). I managed to installed 2.1.0 from the livereload site by temporarily disabling xpinstall.signatures.required.

Edit: it wasn't enough to temporarily disable the config setting, I had to leave it set to false

@jnachtigall
Copy link

Very strange. While it did not work at first, it works now without problems (Ubuntu 14.04 with Firefox 43 and LiveRelead 2.1.1 from AMO). @fredrikekelund fyi

@katherinecory
Copy link

I can't seem to get 2.1.1 or 2.1.0 to work either with Firefox 44. The Chrome and Safari extensions work fine with my dev site but no button appears in FF when I install the extension.

@jnachtigall
Copy link

@katherinecory Sure that the button isn't just hidden under the "hamburger button" > "Customize" and can be added to the toolbar from there? I use LiveReload in Fx 44 on Windows and Ubuntu without problems.

@katherinecory
Copy link

@jnachtigall Now I feel silly! I didn't realise that was an option. Thanks so much, I hope this helps others too 👍

@mgol
Copy link

mgol commented Mar 21, 2016

The AMO extension warns that it's deprecated and advises to install from the developer site where the extension won't work... Should this deprecation warning just be removed and the site upated to point to AMO again?

@JulienItard
Copy link

Up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants