github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 11:28:35 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

Model Edit Page Fails to Persist User Group Assignments When Selecting A Single First User Group #3260

New Issue
Closed
opened 2025-11-11 15:27:12 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-11 15:27:12 -06:00
Owner
Copy Link

Originally created by @jeeteshchel on GitHub (Jan 13, 2025).

Bug Report

Installation Method

Git clone and Docker setup.

Environment

  • Open WebUI Version: v0.5.4
  • Ollama (if applicable): N/A
  • Operating System: Ubuntu 24.04
  • Browser (if applicable): Chrome 131.0.6778.265

Confirmation:

  • I have read and followed all the instructions provided in the README.md.
  • I am on the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:

In Model Edit page, user selects a user group from the dropdown and clicks "Save," the following should occur:

  1. The model update API request for model update should include the selected group_id in the `access_control.read.group_ids array.
  2. Upon reopening the model edit page, the previously selected/saved user group name assignment should be listed.

Actual Behavior:

  1. After selecting a user group and clicking "Save," a success response is displayed, however
  2. The API request for model update shows an empty access_control.read.group_ids array.
  3. When the model edit page is reopened, the selected user group is not displayed as assigned.

Description

Bug Summary:
The application fails to update AccessControl component with the selected user group on form submission, resulting in the group assignment not being persisted.

Steps to Reproduce:

  1. Navigate to the model view/edit page in the Open WebUI.
  2. Select a user group from the dropdown menu under the "Groups" section.
  3. Click the "Save & Update" button.
  4. Observe the success message,.
  5. Check the API request payload for the model update. The access_control.read.group_ids array is empty.
  6. Reopen the model edit page and observe that the selected group is not displayed as assigned.

Logs and Screenshots

Additional Information

  • The issue appears to be related to the front-end failing to properly include the selected group_id in the API request payload.
  • There is no visible error message indicating why the access_control.read.group_ids array remains empty.

Note

If you need further information or assistance in reproducing the bug, feel free to reach out. Thank you for your attention to this issue!

Originally created by @jeeteshchel on GitHub (Jan 13, 2025). ## Bug Report ## Installation Method Git clone and Docker setup. ## Environment - **Open WebUI Version:** v0.5.4 - **Ollama (if applicable):** N/A - **Operating System:** Ubuntu 24.04 - **Browser (if applicable):** Chrome 131.0.6778.265 **Confirmation:** - [x] I have read and followed all the instructions provided in the README.md. - [x] I am on the latest version of both Open WebUI and Ollama. - [ ] I have included the browser console logs. - [ ] I have included the Docker container logs. - [x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below. ## Expected Behavior: In Model Edit page, user selects a user group from the dropdown and clicks "Save," the following should occur: 1. The model update API request for model update should include the selected `group_id` in the `access_control.read.group_ids array. 2. Upon reopening the model edit page, the previously selected/saved user group name assignment should be listed. ## Actual Behavior: 1. After selecting a user group and clicking "Save," a success response is displayed, however 2. The API request for model update shows an empty `access_control.read.group_ids` array. 3. When the model edit page is reopened, the selected user group is not displayed as assigned. ## Description **Bug Summary:** The application fails to update AccessControl component with the selected user group on form submission, resulting in the group assignment not being persisted. **Steps to Reproduce:** 1. Navigate to the model view/edit page in the Open WebUI. 2. Select a user group from the dropdown menu under the "Groups" section. 3. Click the "Save & Update" button. 4. Observe the success message,. 5. Check the API request payload for the model update. The `access_control.read.group_ids` array is empty. 6. Reopen the model edit page and observe that the selected group is not displayed as assigned. ## Logs and Screenshots ## Additional Information - The issue appears to be related to the front-end failing to properly include the selected `group_id` in the API request payload. - There is no visible error message indicating why the `access_control.read.group_ids` array remains empty. ## Note If you need further information or assistance in reproducing the bug, feel free to reach out. Thank you for your attention to this issue!
GiteaMirror commented 2025-11-11 15:27:14 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Jan 13, 2025):

You need to click on the plus button to add.

@tjbck commented on GitHub (Jan 13, 2025): You need to click on the plus button to add.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#3260
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?