Hi S3rch3r, Firefox 48 didn't have the feature used by the current hotfix. Instead, you can try the suggestions from the Firefox 52 ESR threads, such as this and the following replies: https://support.mozilla.org/questions/1258208#answer-1218876

gnappi said

Gads, google is flooded with comments on the web on this problem, I thought I was alone, this has snowballed beyond belief.

You are not alone. Has the problem been solved on your Firefox yet? Seems there are many recent suggestions in your thread here: https://support.mozilla.org/questions/1258230

Thanks jscher2000, Ill look a tad closer at some of that. Unfortunately I am not sure it will help much in this case as you said V48.0.2 didn't have some of the tools or have the feature used by the current hotfix built in to deal with this issue as easily.

The only way atm I have found to fix and it is only temporary until I close and restart Firefox v.48.0.2

The method is to Enable add-on debugging tool in Add-Ons and to select the Load Temporary Add-on.

Fortunately I have found the older ghostery_privacy_ad_blocker-8.0.7.1-an fx.xpi and the older firefox 48 JD Extension (Simply Labeled firefox_48.xpi) and those install and run fine although of course I have to refresh the already opened Web Pages in the currently opened session of the browser.

The problem is of course they don't stick when closing and reopening the browser.

When using the same .xpi extensions though trying to re-add them to the browser, I get the Error that "the file could not be installed as it appears to be corrupt"

So there is something in the about:config that is not there that maybe needed or Firefox/Zozilla has something on their add-on checking url or similar that is not letting use add extensions for older Firefox versions maybe.

Either way it is frustrating and making work on this machine impossibly frustrating when I have to use Firefox.

I know there are a lot of other users on both the Mac and PC side that can not update certain workhorse type machines for various reasons and I would hope the Devs take this into consideration at least for those forced still to use older versions and prefer to use Firefox rather than Chrome or other web browsers on their older machines.

I hope for all this can be figured out by the devs and they do allow some sort of update for with some of these older versions.

Hi S3rch3r, did the method of installing the certificate (from the thread I mentioned in my reply) fail you? I tested on Firefox 52; I can't test on Firefox 48.

The hotfix-update-xpi-intermediate@mozilla com-1 0 2-signed installed just fine, but I still can't reinstall or re-enable the extensions I need to re-enable as I get the Error that "the file could not be installed as it appears to be corrupt" or could not be verified.

So back for the moment to the Enable add-on debugging tool in Add-Ons and to select the Load Temporary Add-on. ....smh :(

I mean these steps:

jscher2000 said

Hi S3rch3r, Firefox 48 didn't have the feature used by the current hotfix. Instead, you can try the suggestions from the Firefox 52 ESR threads, such as this and the following replies: https://support.mozilla.org/questions/1258208#answer-1218876

I have already tried the xpinstall.signatures.require = false

but have not tried the Console yet and most have also not had success with many of those items.

I am a bit leery on the CRT Item as Although it was from another's certification I am unsure when it will expire as well as what it might allow too.

On a Side note: Has there been anything new for others as I have also had another friend who is using OSX 13 and the latest v66.0.3 I believe that when they booted up yesterday they got the message some could not be verified also and it has not updated yet to allow for the previous ones to re-enable.

Have other things to do and not time atm to experiment any further for now till later ... Firefox/Mozilla isn't making this easy for those that are non technical either.

Hoping to find still a solution for myself and hoping that end users don't get so frustrated to switch to other browsers such as (shiver) Chrome, etc.

S3rch3r said

I have already tried the xpinstall.signatures.require = false

Sorry, that is only for "ESR" builds as far as I know. (Or Android.)

I am a bit leery on the CRT Item as Although it was from another's certification I am unsure when it will expire as well as what it might allow too.

Hopefully an official download will become available so you can trust it more.

Has there been anything new for others as I have also had another friend who is using OSX 13 and the latest v66.0.3 I believe that when they booted up yesterday they got the message some could not be verified also and it has not updated yet to allow for the previous ones to re-enable.

Yes: Add-ons disabled or fail to install on Firefox.

Also, Firefox 66.0.4 is expected to be released later today once it passes testing.