mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 19:08:59 -05:00
[GH-ISSUE #19885] bug: OpenWebUI Bug Report: User Group and Model Image Display Issues #34557
Reference in New Issue
Block a user
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?
Originally created by @jotaperez3 on GitHub (Dec 11, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/19885
Check Existing Issues
Installation Method
Git Clone
Open WebUI Version
0.6.41
Ollama Version (if applicable)
No response
Operating System
Windows
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
User Group Selection Bug:
When adding users to a group in the "Edit User Group" section, users should be able to select checkboxes on any page within the "Users" list. The interface should retain the user's current page selection after checking a user.
Model Image Display Bug:
Upon selecting a user on any page other than the first, the interface unexpectedly redirects the user back to the first page of the user list. This disrupts the selection process.
Actual Behavior
User Group Selection Bug:
Upon selecting a user on any page other than the first, the interface unexpectedly redirects the user back to the first page of the user list. This disrupts the selection process.
Model Image Display Bug:
Although the new image appears to be saved in the model settings, the chat window continues to display the default OpenWebUI icon. The custom image change is not reflected.
Steps to Reproduce
Logs & Screenshots
N/A
Additional Information
No response
@owui-terminator[bot] commented on GitHub (Dec 11, 2025):
🔍 Similar Issues Found
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
#19588 issue: Model group permissions
by apunkt • Nov 29, 2025 •
bug#19711 issue: Editing function for models broken
by skleffmann • Dec 03, 2025 •
bug#19861 issue:
by QuitHub • Dec 10, 2025 •
bug#19877 issue:
by dotmobo • Dec 11, 2025 •
bug#19864 issue:
by Haervwe • Dec 10, 2025 •
bugShow 5 more related issues
#19777 issue:
by Yaute7 • Dec 05, 2025 •
bug#19426 issue: Strange Behavior With Groups
by matthew-kusz • Nov 24, 2025 •
bug#19461 issue: Models shared with write permission to group no longer visible in workspace
by destination-one • Nov 25, 2025 •
bug#19563 issue:
by naruto7g • Nov 28, 2025 •
bug#16255 issue: 404: Model not found
by wade3po • Aug 04, 2025 •
bug💡 Tips:
This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
@tjbck commented on GitHub (Dec 11, 2025):
@silentoplayz confirmation wanted here
@silentoplayz commented on GitHub (Dec 11, 2025):
I can confirm this is an issue, yes. The user expects to stay on the page they were viewing, even if a checkbox is clicked next to a user, rather than being unexpectedly taken back to the first page of users to select from in the
Edit User Groupmodal.The model's avatar image is not being updated automatically in the list of models via the
Modelspage of the admin settings. It is a cache issue. I believe the admin panel models list would benefit from cache busting (Cache-control headers to prevent stale cached images), particularly for the model avatar images.Editing the model after saving an avatar image for it reveals an avatar image is still set, despite it not being visible in the list of models via the
Modelspage of the admin settings. The default model avatar is used here still instead.The model's avatar image IS being updated automatically in the model drop-down selector.
@Classic298 commented on GitHub (Dec 14, 2025):
@silentoplayz freebie?
@silentoplayz commented on GitHub (Dec 15, 2025):
Thoughts on adding cache busting (Cache-control headers to prevent stale cached images), particularly for the model avatar images in the models list here?
@silentoplayz commented on GitHub (Dec 21, 2025):
Should be solved on the
devbranch!