mirror of
https://github.com/arkenfox/user.js.git
synced 2024-11-22 02:21:38 +01:00
Page:
3.4 Apply & Update & Maintain
Pages
1.1 To Arkenfox or Not
2.1 User.js
2.2 Backup
3.1 Overrides
3.2 Overrides [Common]
3.3 Overrides [To RFP or Not]
3.4 Apply & Update & Maintain
3.5 prefsCleaner
4.1 Extensions
5.1 Updater [Options]
5.2 Troubleshooting
Appendix A Test Sites
Appendix B Test Sites [Fingerprinting]
Appendix C References
Home
0
3.4 Apply & Update & Maintain
Thorin-Oakenpants edited this page 2023-11-29 06:26:26 +00:00
Table of Contents
🟩 Previous: Overrides [To RFP or Not]
🟪 APPLY
If you are not using a new profile, we recommend running our cleanup script, the instructions are in the file.
- 🔹 Put all the relevant files into the root folder of your profile [1]
- prefsCleaner
- updater
- user.js [NOTE: Do not edit this file directly]
- user-overrides.js [NOTE: this is the file you created, you edit this file with your changes]
- 🔽 CONTINUE with the UPDATE part below
1 To find your profile, open about:support
and look for Profile Folder
under Application Basics
.
🟪 ESR USERS
- 🔹 While it is recommended that users use the arkenfox release that matches their Firefox version, it isn't mandatory
- 🔸 option one (recommended)
- Stick with the matching arkenfox version, and not use the updater. You would then need to;
- Update the
user.js
manually once each ESR major release to match, as arkenfox will already be past that version - Append and update your overrides manually to the end of the
user.js
(and keep a copy)
- Update the
- Stick with the matching arkenfox version, and not use the updater. You would then need to;
- 🔸 option two
- Use the updater (with the
-esr
command, and this will append youruser-overrides.js
, and of course run prefsCleaner - This may cause compatibility or protection issues, as arkenfox is designed per release. The onus is on you.
- Use the updater (with the
🟪 UPDATE
- 🔹 Run the updater
- so the contents of your
user-overrides.js
is appended to theuser.js
- so the contents of your
- 🔹 ALWAYS run prefsCleaner
- make sure Firefox is closed
- this will reset prefs that aren't needed or can cause issues, as well as keep things clean and tidy
- you can read more about prefsCleaner next
🟥 UPDATE ERROR
- 🔹 If you get an
Update failed. Make sure Powershell is allowed internet access
error- run as administrator
- if you still get the error, then run
Get-ChildItem env:\__PSLockDownPolicy
- if you have a PSLockDownPolicy, change it to
Full Language Mode
(value 8)
- if you have a PSLockDownPolicy, change it to
🟪 MAINTAIN
Each release 1, or whenever you modify your user-overrides.js
- 🔹 Check for the latest changelog
- 🔹 Run the updater
- so the contents of your
user-overrides.js
is appended to the NEWuser.js
- so the contents of your
- 🔹 Run prefsCleaner
🟪 RSS FEEDS
- 🔹 releases 1 - https://github.com/arkenfox/user.js/releases.atom
- 🔹 commits - https://github.com/arkenfox/user.js/commits/master.atom
1 Arkenfox changes to the live master user.js
happen once per release: all changes are done in a separate branch and only merged when finished. There is no guarantee when it is done - hopefully within a week of the Firefox release. Nothing of consequence (in the user.js) changes these days that will affect you in that time delay. Do not wait on arkenfox to update Firefox.
🟩 Next: prefsCleaner