Read only variable are user editable #533

Closed
opened 2026-02-05 17:44:32 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @QuintenQVD0 on GitHub (Dec 28, 2025).

Originally assigned to: @Boy132 on GitHub.

Current Behavior

When you create an egg ENV variable with the rules integer and between:1024,65535 and set it to user permission to Viewable, then you can still edit it on the client side.

Expected Behavior

An env variable with only the Viewable permission should not be user editable

Edit: Seems like no read-only variables are correctly validated as I can edit them all?

Steps to Reproduce

  1. Create a random egg with 1 env variable
  2. Set the validation rules to integer and between:1024,65535 and checkbox Viewable
  3. Create a server with it
  4. Go to the startup tab
  5. Try to change the number with the arrows or just typing it.
  6. See it save while it should be read-only

Panel Version

beta30

Wings Version

develop

Games and/or Eggs Affected

All

Docker Image

/

Error Logs


Is there an existing issue for this?

  • I have searched the existing issues before opening this issue.
  • I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server.
  • I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
Originally created by @QuintenQVD0 on GitHub (Dec 28, 2025). Originally assigned to: @Boy132 on GitHub. ### Current Behavior When you create an egg ENV variable with the rules integer and between:1024,65535 and set it to user permission to Viewable, then you can still edit it on the client side. ### Expected Behavior An env variable with only the Viewable permission should not be user editable Edit: Seems like no read-only variables are correctly validated as I can edit them all? ### Steps to Reproduce 1. Create a random egg with 1 env variable 2. Set the validation rules to integer and between:1024,65535 and checkbox Viewable 3. Create a server with it 4. Go to the startup tab 5. Try to change the number with the arrows or just typing it. 6. See it save while it should be read-only ### Panel Version beta30 ### Wings Version develop ### Games and/or Eggs Affected All ### Docker Image / ### Error Logs ```bash ``` ### Is there an existing issue for this? - [x] I have searched the existing issues before opening this issue. - [x] I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server. - [x] I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
Author
Owner

@coderabbitai[bot] commented on GitHub (Dec 28, 2025):

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

  • Create Plan
Examples

🔗 Similar Issues

Related Issues

👤 Suggested Assignees

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

@coderabbitai[bot] commented on GitHub (Dec 28, 2025): <!-- This is an auto-generated issue plan by CodeRabbit --> ### 📝 CodeRabbit Plan Mode Generate an implementation plan and prompts that you can use with your favorite coding agent. - [ ] <!-- {"checkboxId": "8d4f2b9c-3e1a-4f7c-a9b2-d5e8f1c4a7b9"} --> Create Plan <details> <summary>Examples</summary> - [Example 1](https://github.com/coderabbitai/git-worktree-runner/issues/29#issuecomment-3589134556) - [Example 2](https://github.com/coderabbitai/git-worktree-runner/issues/12#issuecomment-3606665167) </details> --- <details> <summary><b>🔗 Similar Issues</b></summary> **Related Issues** - https://github.com/pelican-dev/panel/issues/1469 - https://github.com/pelican-dev/panel/issues/1240 - https://github.com/pelican-dev/panel/issues/1403 - https://github.com/pelican-dev/panel/issues/1115 - https://github.com/pelican-dev/panel/issues/1843 </details> <details> <summary><b>👤 Suggested Assignees</b></summary> - [SirEndii](https://github.com/SirEndii) - [DjordyKoert](https://github.com/DjordyKoert) - [parataku](https://github.com/parataku) - [TigerGamer134](https://github.com/TigerGamer134) - [m41denx](https://github.com/m41denx) </details> --- <details> <summary> 🧪 Issue enrichment is currently in open beta.</summary> You can configure auto-planning by selecting labels in the issue_enrichment configuration. To disable automatic issue enrichment, add the following to your `.coderabbit.yaml`: ```yaml issue_enrichment: auto_enrich: enabled: false ``` </details> 💬 Have feedback or questions? Drop into our [discord](https://discord.gg/coderabbit)!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel-pelican-dev#533