Would it be possible to add a selection option, similar to "settings level", to select either "all settings" or "changed settings"
tx
Under expert there is already an all settings page
request is for a choice 'all' or 'changed only' on the all settings page.
Ah right, this was not clear from your request
DL6ER
November 29, 2023, 12:16pm
5
Please try whether
pihole checkout web tweak/settings_changed_only
is about what you would like to have.
pi-hole:development-v6
← pi-hole:tweak/settings_changed_only
opened 12:15PM - 29 Nov 23 UTC
# What does this implement/fix?
Remove settings level selection in favor of a… simple settings level toogle in the same place:
![Screenshot from 2023-11-29 13-13-53](https://github.com/pi-hole/web/assets/16748619/704bfc89-a5fd-41f2-bc49-33f2e4faafcb)
![Screenshot from 2023-11-29 13-13-55](https://github.com/pi-hole/web/assets/16748619/7c8db1ec-1d1c-4cc0-ac8c-abab36560a86)
Furthermore, we add a feature requested on Discourse: A toggle in the empty place on the `All settings` page that allows you to hide all default-valued config options:
![Screenshot from 2023-11-29 13-14-21](https://github.com/pi-hole/web/assets/16748619/ca1f2638-a359-4c36-9d9f-23bf6e37d6b0)
![Screenshot from 2023-11-29 13-14-24](https://github.com/pi-hole/web/assets/16748619/157f7083-6874-401d-92c1-6d34e6a07f04)
---
**Related issue or feature (if applicable):** N/A
**Pull request in [docs](https://github.com/pi-hole/docs) with documentation (if applicable):** N/A
---
**By submitting this pull request, I confirm the following:**
1. I have read and understood the [contributors guide](https://docs.pi-hole.net/guides/github/contributing/), as well as this entire template. I understand which branch to base my commits and Pull Requests against.
2. I have commented my proposed changes within the code.
3. I am willing to help maintain this change if there are issues with it later.
4. It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1)
5. I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html))
## Checklist:
- [x] The code change is tested and works locally.
- [x] I based my code and PRs against the repositories `developmental` branch.
- [x] I [signed off](https://docs.pi-hole.net/guides/github/how-to-signoff/) all commits. Pi-hole enforces the [DCO](https://docs.pi-hole.net/guides/github/dco/) for all contributions
- [x] I [signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) all my commits. Pi-hole requires signatures to verify authorship
- [x] I have read the above and my PR is ready for review.
pihole checkout web tweak/settings_changed_only
/usr/local/bin/pihole: line 30: /etc/pihole/versions: Permission denied
Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y
[✓] Fetching branches from https://github.com/pi-hole/web.git
[i] 20 branches available for Web Admin
[i] Switching to branch: 'tweak/settings_changed_only' from 'refs/heads/fix/ov [✓] Switching to branch: 'tweak/settings_changed_only' from 'refs/heads/fix/overflow-wrap'
[i] Already up to date.