feat(frontend): add script disable functionality with visual indicators #9374
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
✍️ Description
This PR implements a script disable system that allows scripts to be temporarily disabled while remaining visible in the interface with clear explanations. Instead of removing scripts entirely when issues arise, they now display a prominent disabled state with contextual information about why they're unavailable and links to related discussions or fixes.
Key Features:
disable: truewith a requireddisable_descriptionexplaining the reasonopnsense-vm.jsonProblem Solved:
Previously, problematic scripts were removed entirely, causing confusion for users trying to find them. This new system keeps scripts discoverable while clearly communicating their status, enabling community contributions toward fixes and maintaining transparency about known issues.
Screenshots
Dark Mode
Light Mode
🔗 Related PR / Issue
Link: #6183
✅ Prerequisites (X in brackets)
🛠️ Type of Change (X in brackets)
README,AppName.md,CONTRIBUTING.md, or other docs.