[Signed fixed extension attached] CB broken on Firefox 48+

[Odyseus]

The requested topic does not exist.

I bet a Mozilla developer asked a moderator to delete the topic.

The Mozilla Russian forums still has several topics with that tweak published.
How to disable verification of digital signatures in extensions
The patch for Firefox 48 for unsigned add-ons

I guess the hack will stop working in a future version.

Well, like everything coming from Mozilla these couple of years, lets enjoy it while it lasts.

Has this extension been abandoned?

Custom Buttons extension was last updated just 4 months ago, not 4 years. I'm sure that the author has better things to do than to keep up fixing errors caused by the decisions of a moronic corporation.

Is there any hope for an update?

When the author feels like it. In the mean time, there are several ways to make the extension work in all versions of Firefox.

[avada]

Attached to this post is the extension with the changes specified above applied plus the fix described in this other bug. Both extensions, the one in this post and the one in the other post, are exactly the same file.

Rename the .zip file extension to .xpi to install

Thanks for the fix. This seems to have fixed my broken buttons. Oddly enough CB worked without issue until today, but it's supposed to be broken for months now. Oh, well. Lucky I remembered this forum from the last breakage.

[Hippopotamus]

Updated today to v51.0a2 only to discover that all my custom buttons had stopped working (with add-on v0.0.5.8.9 from AMO). Installed Odyseus' fix in the OP instead and everything works perfectly well. Thanks!

[thadrummer]

Is there any way of making CB work on the official 51.0b1 at the moment?
Due to the add on signing requirement I can't install Odyseus' fix and I really don't want to change my Firefox version right now.

Any help would be appreciated.

[trapper john]

Is there any way of making CB work on the official 51.0b1 at the moment?
Due to the add on signing requirement I can't install Odyseus' fix and I really don't want to change my Firefox version right now.

Any help would be appreciated.

if antonglv doesn't return by 51's release perhaps someone else on the forum could get it signed and then we can all download it. Maybe we can draw straws to see who'll do it lol.

An alternative for now is to do what I'm doing, instead of the beta go with aurora 52, it still works in that.

[thadrummer]

if antonglv doesn't return by 51's release perhaps someone else on the forum could get it signed and then we can all download it. Maybe we can draw straws to see who'll do it lol.

An alternative for now is to do what I'm doing, instead of the beta go with aurora 52, it still works in that.

I would do that except for the fact that even on 51.0b1, I can feel the browser being in beta (unexpected slowdowns and snags every now and then etc.). Going on the alpha channel, I think, would exacerbate this underlying behavior even more because of the nature of a piece of software being in an alpha build.

What I was considering, actually, was to just switch to the official version, 50, where CB should still work. Then, if by the time the official release reaches 51, CB isn't fixed, I would look for an alternative like Autohotkey to implement similar tools to what I currently use. I would have just preferred to still use a built in solution to achieve the same result.
Here's hoping.

[Odyseus]

Hello, g@ys.

@thadrummer: Just disable add-ons signing and use any unsigned extension on any Firefox version. For disabling add-on signing on Firefox stable/beta, use this method. Or you can even use an unbranded version of Firefox.

@trapper john: Nobody will bother to upload a patched version of this or any other XUL based add-on. Mozilla had planned to block the upload of these type of add-ons to AMO (addons.mozilla.org). I don't know if it's implemented yet, but that isn't the only annoyance. The most problematic is the need to change the add-on UUID, even if one wants to just sign it without publishing it.

So, to cut it short, disable add-on signing and move on.

[trapper john]

Forgot about that trick for disabling add-on signing, it was on mozillazine but got removed if I recall. That's certainly an option if all else fails, thanks Odyseus for the link.

@thadrummer, if you try the hack to disable add-on signing let us know if it works.

[mcee]

Use Waterfox - no signing needed.

[trapper john]

Use Waterfox - no signing needed.

Would love to except I'm stuck on Win 7 32-bit. Might be a good option for others though.

Have to admit, I'd very much like to move onto something else at this point given the performance decline in the nightlies with video playing and other issues, not to mention required signings and other mindless ideas. To watch flash videos I'm forced to use IE it's gotten so bad. Flash is flawless on IE11, regardless of hardware or software mode.

Why can't Firefox work like that? A bug was filed but the developer looked at it for a day then abandoned it, not the first time. Then they wonder why they're losing market share. It's very frustrating and the only thing keeping me on this browser are addons like custom buttons and noscript. Without those Firefox would have been long gone.