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 extension not signed #12

Open
tahitiangabriel opened this issue Jan 5, 2016 · 8 comments
Open

Firefox extension not signed #12

tahitiangabriel opened this issue Jan 5, 2016 · 8 comments

Comments

@tahitiangabriel
Copy link

With the latest Firefox (version 43) it is not possible to install the WicketSource extension as the module is not signed.
It would be nice if it was possible for you to sign it...
Please see https://developer.mozilla.org/en-US/Add-ons/Distribution.

@jennybrown8
Copy link
Contributor

Thanks for the note (though I can't seem to view that link?). I'll check into it, but no promises; this isn't getting a lot of my time lately. I think the Chrome extension still works, if you need an alternative.

@tahitiangabriel
Copy link
Author

Jenny, what is wrong with the link?
Every wicket developers should use your extension. It is awesome! I use it everyday!

@jennybrown8
Copy link
Contributor

Looks like the link had the dots removed from the server part of the url when I clicked on it, which gave a DNS error for finding the server (of course). How strange. It looks fine on hover. Anyway I put the dots back in and I can view the page now.

@FeanorsCurse
Copy link

I'd appreciate it as well if the extension was verified - no longer able to use it, though I really liked it.

@tahitiangabriel
Copy link
Author

As a workaround you can disable the signature checking :
-Go to about:config
-Set xpinstall.signatures.required to false.

@toby1984
Copy link

toby1984 commented Aug 5, 2016

The workaround doesn't work anymore in FF 48+ where add-on signing now seems to be mandatory. Could you please have Mozilla sign this very useful extension ? Thanks !

@jennybrown8
Copy link
Contributor

Getting a plugin signed was a non-trivial amount of work. I'm aware of the
need for both firefox and chrome, as well as the Eclipse plugin.
Unfortunately I haven't had the time to really devote to keeping this
maintained. I'd still like to do the updates, but don't expect to see it
soon (sorry). Thank you to those who are posting workarounds; that's all I
can offer at the moment.

On Fri, Aug 5, 2016 at 1:00 AM, Tobias Gierke notifications@github.com
wrote:

The workaround doesn't work anymore in FF 48+ where add-on signing now
seems to be mandatory. Could you please have Mozilla sign this very useful
extension ? Thanks !


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#12 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABAaMK0No7s4Zddg8kmOWT0Ne-8OQg5yks5qctF5gaJpZM4G-g9o
.

@jennybrown8
Copy link
Contributor

jennybrown8 commented Aug 21, 2016

I did some more digging. Due to the shift in Firefox to deprecate XUL extensions, and switch to Web Extensions instead, this requires a complete rewrite from scratch.

Additionally, the Web Extensions API does not yet include the ability to add a pane as a sidebar to the Inspect feature of the Dev Tools. I also checked Firebug, and it's also undergoing a serious rewrite (see Firebug.next / Firebug 3 beta) and is not in release yet for the stable channel of Firefox. So, basically we're stuck on a firefox extension until the extension APIs stabilize.

I have updated the Chrome extension and it's installable from the Chrome Web Store; it should be working again.

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

4 participants