mirror of
https://github.com/open-webui/open-webui.git
synced 2026-07-16 05:47:50 -05:00
[GH-ISSUE #20284] issue: Custom Pending User Overlay Text Not Displaying on Mobile #57806
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 @sophia-xu-upskill on GitHub (Dec 30, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20284
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.41
Ollama Version (if applicable)
No response
Operating System
Amazon Linux 2
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
When a new user registers on Open WebUI, the pending user overlay page should display custom text configured by the administrator. This should work correctly on both desktop and mobile browsers.
Actual Behavior
When a new user registers on Open WebUI, the pending user overlay page should display custom text configured by the administrator. This works correctly on desktop browsers but fails on mobile browsers, which show the default system text instead.
Steps to Reproduce
As an admin, configure custom text for pending user overlay in the admin panel, see attached screenshot.
Register a new user account on a desktop browser, after click "Create Account" button:
✅ Expected: Custom configured text is displayed
✅ Result: Works correctly - custom text is shown
Register a new user account on a mobile browser, after click "Create Account" button:
✅ Expected: Same custom configured text should be displayed
❌ Result: Default system text is shown instead
Alternative for step 3:
✅ Expected: Same custom configured text should be displayed
❌ Result: Default system text is shown instead
Logs & Screenshots
Additional Information
Type Definition Mismatch issue:
There's an inconsistency in the TypeScript type definition:
Backend returns: pending_user_overlay_content
Type definition in src/lib/stores/index.ts has: pending_user_overlay_description
While this shouldn't affect runtime behavior, it indicates potential confusion in the codebase.
@owui-terminator[bot] commented on GitHub (Dec 30, 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:
#20019 issue:
by j63440490 • Dec 17, 2025 •
bug#19777 issue:
by Yaute7 • Dec 05, 2025 •
bug#19864 issue:
by Haervwe • Dec 10, 2025 •
bug#19987 issue: There is a lack of visual consistency between the home page and the chat interface.
by i-iooi-i • Dec 16, 2025 •
bug#19877 issue:
by dotmobo • Dec 11, 2025 •
bugShow 5 more related issues
#20092 issue:
by VideoRyan • Dec 22, 2025 •
bug#19861 issue:
by QuitHub • Dec 10, 2025 •
bug#19563 issue:
by naruto7g • Nov 28, 2025 •
bug#19211 issue:
by Byrnes9 • Nov 16, 2025 •
bug#19438 issue: Icon loading regression
by JoelShepard • Nov 24, 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.
@Classic298 commented on GitHub (Dec 30, 2025):
are you certain this is not a cache issue or multitenancy issue (redis missing)? if the default text is shown it might be a cache issue from server side or client side caching. i dont think the code handles mobile requests any different than desktop requests 😁
@Classic298 commented on GitHub (Dec 30, 2025):
I investigated the codebase and can confirm part of this issue is valid:
You're correct that there's a type definition inconsistency. The Config type in src/lib/stores/index.ts defines pending_user_overlay_description, but both the backend (main.py) and the component (AccountPending.svelte) correctly use pending_user_overlay_content. I've submitted a PR to fix this.
But after reviewing the code, there's no mobile-specific logic for the pending user overlay - both platforms use the same code path via AccountPending.svelte. As I already said, this is most likely a caching issue (either browser cache, service worker, or Redis misconfiguration issue if using multi-tenancy).