[PR #16383] [CLOSED] Feat/custom image generation #62971

New Issue

GiteaMirror · 2026-05-06T07:27:07-05:00

GiteaMirror commented

2026-05-06 07:27:07 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/16383
Author: @DonInabon
Created: 8/8/2025
Status: ❌ Closed

Base: main ← Head: feat/custom-image-generation

📝 Commits (7)

2895c91 feat: Add support for custom image generation API
8228277 I have corrected the custom image generation logic. The previous implementation had a SyntaxError because the image generation logic was incorrectly placed in the get_models function. I moved the logic to the /generations endpoint and made the get_models function return an empty list for the custom engine.
e681658 fix: Refactor custom image generation config variables
8e17c80 fix: Register custom image generation config variables
8c4b571 fix: Hide unnecessary fields for custom image generation engine
5cba40b fix: Handle missing content-type for custom image generation
e087ff9 feat: Add support for custom image generation API

📊 Changes

4 files changed (+226 additions, -49 deletions)

View changed files

📝 backend/open_webui/config.py (+28 -0)
📝 backend/open_webui/main.py (+10 -0)
📝 backend/open_webui/routers/images.py (+72 -1)
📝 src/lib/components/admin/Settings/Images.svelte (+116 -48)

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.

Before submitting, make sure you've checked the following:

Target branch: Please verify that the pull request targets the dev branch.
Description: Provide a concise description of the changes made in this pull request.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
Testing: Have you written and run sufficient tests to validate the changes?
Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
- BREAKING CHANGE: Significant changes that may affect compatibility
- build: Changes that affect the build system or external dependencies
- ci: Changes to our continuous integration processes or workflows
- chore: Refactor, cleanup, or other non-functional code changes
- docs: Documentation update or addition
- feat: Introduces a new feature or enhancement to the codebase
- fix: Bug fix or error correction
- i18n: Internationalization or localization changes
- perf: Performance improvement
- refactor: Code restructuring for better maintainability, readability, or scalability
- style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
- test: Adding missing tests or correcting existing tests
- WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

[Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)]

Added

[List any new features, functionalities, or additions]

Changed

[List any changes, updates, refactorings, or optimizations]

Deprecated

[List any deprecated functionality or features that have been removed]

Removed

[List any removed features, files, or functionalities]

Fixed

[List any fixes, corrections, or bug fixes]

Security

[List any new or updated security-related changes, including vulnerability fixes]

Breaking Changes

BREAKING CHANGE: [List any breaking changes affecting compatibility or functionality]

Additional Information

[Insert any additional context, notes, or explanations for the changes]
- [Reference any related issues, commits, or other relevant information]

Screenshots or Videos

[Attach any relevant screenshots or videos demonstrating the changes]

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/16383 **Author:** [@DonInabon](https://github.com/DonInabon) **Created:** 8/8/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `feat/custom-image-generation` --- ### 📝 Commits (7) - [`2895c91`](https://github.com/open-webui/open-webui/commit/2895c91d42d9a1e93239e4fb71c545c92de82aa5) feat: Add support for custom image generation API - [`8228277`](https://github.com/open-webui/open-webui/commit/82282772bbdbb9b3f290425cc56b4dd417504d54) I have corrected the custom image generation logic. The previous implementation had a `SyntaxError` because the image generation logic was incorrectly placed in the `get_models` function. I moved the logic to the `/generations` endpoint and made the `get_models` function return an empty list for the custom engine. - [`e681658`](https://github.com/open-webui/open-webui/commit/e681658eb67bc5045df44e1fc9bea6c07239a6e6) fix: Refactor custom image generation config variables - [`8e17c80`](https://github.com/open-webui/open-webui/commit/8e17c80cd4c0231380135d00a23bfbb541e199ad) fix: Register custom image generation config variables - [`8c4b571`](https://github.com/open-webui/open-webui/commit/8c4b5713a7c04502b60ce841b477a73bb3047204) fix: Hide unnecessary fields for custom image generation engine - [`5cba40b`](https://github.com/open-webui/open-webui/commit/5cba40b4fc0f0612d15d147cb1643431d51ce477) fix: Handle missing content-type for custom image generation - [`e087ff9`](https://github.com/open-webui/open-webui/commit/e087ff963e41ed5be619e12dabf2ac7dcd33c71f) feat: Add support for custom image generation API ### 📊 Changes **4 files changed** (+226 additions, -49 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/config.py` (+28 -0) 📝 `backend/open_webui/main.py` (+10 -0) 📝 `backend/open_webui/routers/images.py` (+72 -1) 📝 `src/lib/components/admin/Settings/Images.svelte` (+116 -48) </details> ### 📄 Description # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) and describe your changes before submitting a pull request. **Before submitting, make sure you've checked the following:** - [ ] **Target branch:** Please verify that the pull request targets the `dev` branch. - [ ] **Description:** Provide a concise description of the changes made in this pull request. - [ ] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [ ] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [ ] **Testing:** Have you written and run sufficient tests to validate the changes? - [ ] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [ ] **Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description - [Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)] ### Added - [List any new features, functionalities, or additions] ### Changed - [List any changes, updates, refactorings, or optimizations] ### Deprecated - [List any deprecated functionality or features that have been removed] ### Removed - [List any removed features, files, or functionalities] ### Fixed - [List any fixes, corrections, or bug fixes] ### Security - [List any new or updated security-related changes, including vulnerability fixes] ### Breaking Changes - **BREAKING CHANGE**: [List any breaking changes affecting compatibility or functionality] --- ### Additional Information - [Insert any additional context, notes, or explanations for the changes] - [Reference any related issues, commits, or other relevant information] ### Screenshots or Videos - [Attach any relevant screenshots or videos demonstrating the changes] ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-05-06 07:27:07 -05:00

GiteaMirror closed this issue

2026-05-06 07:27:10 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#62971