starred/panel-pelican-dev
1
0
Fork 0
mirror of https://github.com/pelican-dev/panel.git synced 2026-05-04 18:00:48 +03:00
Code Issues 41 Packages Projects Releases 10 Wiki Activity

Deleting a newly-set primary allocation on a server #166

New Issue
Closed
opened 2026-02-05 17:13:22 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-05 17:13:22 +03:00
Owner
Copy Link

Originally created by @JustNotSebas on GitHub (Oct 6, 2024).

Current Behavior

Discovered this on total accident, but when having an allocation selected on the server edit page, and setting that allocation as primary, it doesn't remove the selection (still appears as 1 record selected even though the checkmark dissapeared), and it allows to dissociate all the allocations on the server, including the primary one, which isn't supposed to be deleted.
image
image

It also makes the address show as "n/a" on the user page.
image

It's not that big of a deal, because you can set back the allocation on the server page, but being that it happened to me by accident, it's best to have it solved to avoid issues.

Expected Behavior

When clicking on "Make Primary", it should remove the selection, or at the very least, have a warning if the user attempts to delete the primary allocation of the server.

Steps to Reproduce

Prerrequisite: Have at least two allocations on the server, one being the primary one.

  1. Select the non-primary allocation, being the only one that can be selected.
  2. With the allocation selected, click "Make Primary"

The allocation will remain selected, even though the checkmark dissapeared.

  • From this point, you can dissociate the allocation, or both of them. Doing this will result on the server losing it's primary allocation.

Panel Version

1.0.0-beta10

Wings Version

1.0.0-beta4

Games and/or Eggs Affected

No response

Docker Image

No response

Error Logs

No response

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 @JustNotSebas on GitHub (Oct 6, 2024). ### Current Behavior Discovered this on total accident, but when having an allocation selected on the server edit page, and setting that allocation as primary, it **doesn't** remove the selection (still appears as 1 record selected even though the checkmark dissapeared), and it allows to dissociate all the allocations on the server, including the primary one, which isn't supposed to be deleted. ![image](https://github.com/user-attachments/assets/8a247ddd-c818-4353-9579-fa9b554849a7) ![image](https://github.com/user-attachments/assets/d610e81d-0663-47ce-a712-53d41c98eae5) It also makes the address show as "n/a" on the user page. ![image](https://github.com/user-attachments/assets/cb5bd35d-cd18-457e-99f2-a6b7818da8bf) It's not that big of a deal, because you can set back the allocation on the server page, but being that it happened to me by accident, it's best to have it solved to avoid issues. ### Expected Behavior When clicking on "Make Primary", it should remove the selection, or at the very least, have a warning if the user attempts to delete the primary allocation of the server. ### Steps to Reproduce Prerrequisite: Have at least two allocations on the server, one being the primary one. 1. Select the non-primary allocation, being the only one that _can_ be selected. 2. With the allocation selected, click "Make Primary" The allocation will remain selected, even though the checkmark dissapeared. - From this point, you can dissociate the allocation, or both of them. Doing this will result on the server losing it's primary allocation. ### Panel Version 1.0.0-beta10 ### Wings Version 1.0.0-beta4 ### Games and/or Eggs Affected _No response_ ### Docker Image _No response_ ### Error Logs _No response_ ### 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.
OVERLORD added the 🟢 easy label 2026-02-05 17:13:22 +03:00
OVERLORD commented 2026-02-05 17:13:30 +03:00
Author
Owner
Copy Link

@notAreYouScared commented on GitHub (Oct 6, 2024):

I think think this would be a filament bug as that's all handled by it and it's packages.

@notAreYouScared commented on GitHub (Oct 6, 2024): I think think this would be a filament bug as that's all handled by it and it's packages.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
not confirmed
pull-request
Mirrored from GitHub Pull Request
 👑 sponsor
💰 fund
🔴 hard
🟡 medium
🟡 medium
🟡 medium
🟢 easy
🟢 easy
🟢 easy
No Label 🟢 easy
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel-pelican-dev#166
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?