Original thread title: Arkenfox’s user.js DISABLES the Enterprise Policies service?!?
2nd thread title: How do I port Waterfox Classic to Firefox ESR 78 without crashing?
Current thread title related to post 7:
Prior to using Arkenfox’s user.js directly, I ported over most of the settings I needed by using about:config. This was working with a policies.json I was using and there wasn’t anything wrong with it.
As soon as I added the real Arkenfox user.js, policies.json stopped working. about:policies
just keeps showing a syntax error in the JSON file.
WHAT THE HELL IS WRONG?!? I made sure the syntax is correct in the JSON file in Kate and the Arkenfox user.js is parsing correctly all the way to the end. Is there a hidden killswitch? Is Mozilla secretly looking at people doing this and adding a bug as a “feature?” I have lost all my patience and cannot stand another roadblock to upgrading to a modern browser.
I couldn’t even port my Waterfox Classic profile to ESR 78 without instant crashes so I am about to lose it.
This is no time for these issues whilst I’m on the edge of sanity without landline internet and nobody else seems to be of help, suspecting Mozilla for putting in hidden killswitches.
Learning Waterfox Classic being dead is traumatic enough, now you won’t let me port my profile, NOR allow policies.json and the Arkenfox user.js to parse simultaneously. I can’t even begin to think about how to parse a user-overrides.js
from 12Bytes’ site.
I DOUBLE CHECKED AND TRIPLE CHECKED THE SYNTAX. IT’S CORRECT.
SO THEN WHY THE HELL IS IT NOT WORKING!?!
Edit: I added an extra comma at the end…
so where it was supposed to be
"DisableTelemetry": true
}
it was
"DisableTelemetry": true,
}
This took me literal hours to figure out because I don’t main in programming.
I still have trouble migrating my Waterfox Classic profile so the crisis is not over yet.
Edit 2: See post 7, got a huge bone to pick with about:logins