[OTHER] Specialized configs page is not available 21.5.2026 #292

GW72 commented 2026年05月21日 06:20:31 +02:00

Please explain your inquiry.

It could be due to current updating of the site, but in the manual configurations section of the main page, when specialized configs is clicked (URL = https://codeberg.org/celenity/Phoenix#-specialized-configs) I arrive back at the main page. I am looking to check for an updated youtube config, but can't get to the file.

### Please explain your inquiry. It could be due to current updating of the site, but in the manual configurations section of the main page, when `specialized configs `is clicked (URL = `https://codeberg.org/celenity/Phoenix#-specialized-configs`) I arrive back at the main page. I am looking to check for an updated `youtube config`, but can't get to the file.

celenity commented 2026年05月21日 08:03:27 +02:00

Hey @GW72 I apologize for any confusion/inconvenience here.

So, basically, as part of the restructuring with 2026年05月21日.1, instead of having a separate config file for each specialized config, Phoenix's specialized configs are now technically set from just one file, phoenix-specialized.cfg - so that's the file you'll want to update for the specialized configs going forward. It can be found at specs/phoenix-specialized.cfg within Phoenix's release archives - and is also located here within the repo (though I'd recommend getting it from the archive, in case we need to add logic to parse that file in the future).

You'll want to update the user.js for your YouTube profile as well - the new one can be found here. The old/current user.js file you're using should still work, but I'd recommend updating to the new file to avoid any future issues.

Please LMK if you have any issues!

Hey @GW72 I apologize for any confusion/inconvenience here. So, basically, as part of the restructuring with `2026年05月21日.1`, instead of having a separate config file for each specialized config, Phoenix's specialized configs are now technically set from just one file, `phoenix-specialized.cfg` - so that's the file you'll want to update for the specialized configs going forward. It can be found at `specs/phoenix-specialized.cfg` within Phoenix's release archives - and is also located [here within the repo](https://codeberg.org/celenity/Phoenix/src/branch/dev/specs/phoenix-specialized.cfg) *(though I'd recommend getting it from the archive, in case we need to add logic to parse that file in the future)*. You'll want to update the `user.js` for your YouTube profile as well - the new one can be found [here](https://codeberg.org/celenity/Phoenix/src/branch/dev/specs/userjs/youtube/user.js). The old/current `user.js` file you're using should still work, but I'd recommend updating to the new file to avoid any future issues. Please LMK if you have any issues!

GW72 commented 2026年05月21日 19:30:44 +02:00

Thanks for the clarifications. I think I might of been trying the youtube config update business at the same time you were updating the website. I think that is sorted but now I have a question about my entended profile.

The instructions are to take the user.js from /etc/firefox/phoenix/userjs/extended/user.js and drop it in the FF profile directory. But in /etc/firefox/phoenix/userjs all I see is a README file. There is no extended directory. I will go back to the main page and try to find my way but I thought it was interesting that the directory is missing.

EDIT: I can't find the extended user.js on the site. Should I just make my own user.js file in the same spirit as the youtube config, as in: user_pref("browser.phoenix.specConfig", "extended");

Thanks for the clarifications. I think I might of been trying the youtube config update business at the same time you were updating the website. I think that is sorted but now I have a question about my `entended` profile. The instructions are to take the `user.js` from `/etc/firefox/phoenix/userjs/extended/user.js` and drop it in the FF profile directory. But in `/etc/firefox/phoenix/userjs` all I see is a README file. There is no `extended` directory. I will go back to the main page and try to find my way but I thought it was interesting that the directory is missing. EDIT: I can't find the extended `user.js` on the site. Should I just make my own `user.js` file in the same spirit as the `youtube config`, as in: `user_pref("browser.phoenix.specConfig", "extended");`

celenity commented 2026年05月21日 22:47:41 +02:00

So basically @GW72, there’s no longer a specialized coding for Phoenix Extended - it’s now handled within the same file as Phoenix is directly (phoenix.cfg).

To enable Phoenix Extended, you can set browser.phoenix.extended to true and restart the browser. You don’t really need a user.js for it anymore (which is why it no longer exists), but if you want to make one anyways, you would want to modify it to:

user_pref("browser.phoenix.extended", true);

So basically @GW72, there’s no longer a specialized coding for Phoenix Extended - it’s now handled within the same file as Phoenix is directly *(`phoenix.cfg`)*. To enable Phoenix Extended, you can set `browser.phoenix.extended` to `true` and restart the browser. You don’t really need a `user.js` for it anymore *(which is why it no longer exists)*, but if you want to make one anyways, you would want to modify it to: ``` user_pref("browser.phoenix.extended", true); ```

GW72 commented 2026年05月22日 07:16:22 +02:00

Ok, again, thanks for the clarifications. Perhaps the following webpage should be reworked to reflect what is required: https://codeberg.org/celenity/Phoenix/src/branch/dev/docs/Extended.md which is where you end up after clicking Installation --> Extended (https://codeberg.org/celenity/Phoenix#extended) on the main page.

Specifically an update is required for:

Default
1: Install Phoenix via the script for your platform of choice above.
2: After installation is complete, locate the Extended user.js file on your device.
# Default
/etc/firefox/phoenix/userjs/extended/user.js
# Flatpak
/var/lib/flatpak/app/org.mozilla.firefox/current/active/files/etc/firefox/phoenix/userjs/extended/user.js
# Apple Silicon
/opt/homebrew/opt/phoenix-osx/userjs/extended/user.js
# Intel
/usr/local/opt/phoenix-osx/userjs/extended/user.js
3: Find your Firefox profile's directory. This depends on your platform, but an easy way to find it is by navigating to about:profiles, and it'll be the path listed beside Root Directory. For example's sake, we'll say our profile's directory is /home/$(whoami)/.mozilla/firefox/153acxao.default-release. Yours will be different, and you should replace this path on the next step with your actual profile directory's path.
4: Simply move (or copy & paste) your user.js file to your profile's directory! You can either drag and drop it manually, or run the command below. For example's sake, we'll say our user.js is located at /etc/firefox/phoenix/userjs/extended/user.js. Yours may be different, and you should replace this path on the next step with the actual location of your user.js as described above.
cp /etc/firefox/phoenix/userjs/extended/user.js /home/$(whoami)/.mozilla/firefox/153acxao.default-release/user.js

Ok, again, thanks for the clarifications. Perhaps the following webpage should be reworked to reflect what is required: `https://codeberg.org/celenity/Phoenix/src/branch/dev/docs/Extended.md` which is where you end up after clicking `Installation --> Extended` (`https://codeberg.org/celenity/Phoenix#extended`) on the main page. Specifically an update is required for: ``` Default 1: Install Phoenix via the script for your platform of choice above. 2: After installation is complete, locate the Extended user.js file on your device. # Default /etc/firefox/phoenix/userjs/extended/user.js # Flatpak /var/lib/flatpak/app/org.mozilla.firefox/current/active/files/etc/firefox/phoenix/userjs/extended/user.js # Apple Silicon /opt/homebrew/opt/phoenix-osx/userjs/extended/user.js # Intel /usr/local/opt/phoenix-osx/userjs/extended/user.js 3: Find your Firefox profile's directory. This depends on your platform, but an easy way to find it is by navigating to about:profiles, and it'll be the path listed beside Root Directory. For example's sake, we'll say our profile's directory is /home/$(whoami)/.mozilla/firefox/153acxao.default-release. Yours will be different, and you should replace this path on the next step with your actual profile directory's path. 4: Simply move (or copy & paste) your user.js file to your profile's directory! You can either drag and drop it manually, or run the command below. For example's sake, we'll say our user.js is located at /etc/firefox/phoenix/userjs/extended/user.js. Yours may be different, and you should replace this path on the next step with the actual location of your user.js as described above. cp /etc/firefox/phoenix/userjs/extended/user.js /home/$(whoami)/.mozilla/firefox/153acxao.default-release/user.js ```

celenity commented 2026年05月22日 08:39:10 +02:00

Thank you! I Just updated that documentation page.

One more thing I forgot to mention - @GW72 after updating (or removing) your user.js files for Phoenix Extended and for your specialized configs (and after restarting the browser/confirming that autoadmin.global_config_url is set to an empty value, from about:config) - make sure to set browser.phoenix.usingLegacySpecConfig to false from about:config. It's not a big deal if you don't, but it just ensures you won't run an unnecessary migration check on each launch.

Thank you! I Just updated that documentation page. One more thing I forgot to mention - @GW72 after updating *(or removing)* your `user.js` files for Phoenix `Extended` *and* for your specialized configs *(and after restarting the browser/confirming that `autoadmin.global_config_url` is set to an empty value, from [`about:config`](about:config))* - make sure to set `browser.phoenix.usingLegacySpecConfig` to `false` from [`about:config`](about:config). It's not a big deal if you don't, but it just ensures you won't run an unnecessary migration check on each launch.