github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-08 04:16:03 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

issue: disabling a model persists all details #4284

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

Originally created by @stevenh on GitHub (Mar 6, 2025).

Check Existing Issues

  • I have searched the existing issues and discussions.

Installation Method

Docker

Open WebUI Version

v0.5.20

Ollama Version (if applicable)

No response

Operating System

macos sequioa

Browser (if applicable)

No response

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have checked the browser console logs.
  • I have checked the Docker container logs.
  • I have listed steps to reproduce the bug in detail.

Expected Behavior

If a pipe or source data is updated renaming a model that hasn't been customised by the user I would expect the new name to be applied.

Actual Behavior

Old names are persisted if the user has made any changes to model, most importantly if toggled the enable / disable switch.

Steps to Reproduce

  1. Install and configure a key for OpenRouter pipe
  2. View the models page in Admin Settings > Models.
  3. Toggle one of the OpenRouter models to disable it from showing.
  4. Edit the OpenRouter settings and change the Model Prefix
  5. Revisit the models page in Admin Settings > Models.
  6. Observe that the model which was disabled didn't change the prefix.

While OpenRouter provides an easy way to test as it includes the Model Prefix option, any pipe or data source which changed the name of a model would trigger this issue.

Logs & Screenshots

Here's a screenshot of where I changed the prefix a few times the last three models we never toggled the first was and has now had it's name persisted.
Image

Additional Information

The cause for this is all details are persisted about a model if any change is made which includes toggling its status. The code responsible for this is here.

I would suggest that names should only be persisted if edited, allowing pipes to update them successfully.

Originally created by @stevenh on GitHub (Mar 6, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Installation Method Docker ### Open WebUI Version v0.5.20 ### Ollama Version (if applicable) _No response_ ### Operating System macos sequioa ### Browser (if applicable) _No response_ ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have checked the browser console logs. - [x] I have checked the Docker container logs. - [x] I have listed steps to reproduce the bug in detail. ### Expected Behavior If a pipe or source data is updated renaming a model that hasn't been customised by the user I would expect the new name to be applied. ### Actual Behavior Old names are persisted if the user has made any changes to model, most importantly if toggled the enable / disable switch. ### Steps to Reproduce 1. Install and configure a key for [OpenRouter pipe](https://openwebui.com/f/rburmorrison/openrouter) 2. View the models page in [Admin Settings ](http://localhost:3000/admin/settings)> Models. 3. Toggle one of the OpenRouter models to disable it from showing. 4. Edit the OpenRouter settings and change the Model Prefix 5. Revisit the models page in [Admin Settings ](http://localhost:3000/admin/settings)> Models. 6. Observe that the model which was disabled didn't change the prefix. While OpenRouter provides an easy way to test as it includes the Model Prefix option, any pipe or data source which changed the name of a model would trigger this issue. ### Logs & Screenshots Here's a screenshot of where I changed the prefix a few times the last three models we never toggled the first was and has now had it's name persisted. ![Image](https://github.com/user-attachments/assets/7ab53371-49be-45de-a32c-f0c58d5a94a6) ### Additional Information The cause for this is all details are persisted about a model if any change is made which includes toggling its status. The code responsible for this is [here](https://github.com/open-webui/open-webui/blob/3b70cd64d7fa6902e8c79cf8dcbf3c7e84cf704b/backend/open_webui/utils/models.py#L112). I would suggest that names should only be persisted if edited, allowing pipes to update them successfully.
GiteaMirror added the bug label 2025-11-11 15:50:35 -06:00
GiteaMirror commented 2025-11-11 15:50:36 -06:00
Author
Owner
Copy Link

@stevenh commented on GitHub (Mar 6, 2025):

The only workaround I've found so far is export the DB, delete the offending rows and then import the db using the details provided here.

@stevenh commented on GitHub (Mar 6, 2025): The only workaround I've found so far is export the DB, delete the offending rows and then import the db using the details provided [here](https://docs.openwebui.com/tutorials/database/).
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 bug
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#4284
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?