langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[Bug]: Unable to save settings in "Conversation Opener" modal #22132

New Issue
Closed
opened 2026-02-21 20:15:54 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 20:15:54 -05:00
Owner
Copy Link
Copy Source

Originally created by @kevintsai1202 on GitHub (Feb 6, 2026).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.12.1

Cloud or Self Hosted

Cloud

Steps to reproduce

  • Go to the "Conversation Opener" settings.
  • Add a new opening question (e.g., "abc").
  • (Note: The main opener text field is currently empty as shown in the screenshot).
  • Observe that the "Save" (儲存) button is disabled/unresponsive.

✔️ Expected Behavior

The "Save" button should be active and allow me to save the conversation opener settings, or show a clear validation error if a required field is missing.

❌ Actual Behavior

Image
Originally created by @kevintsai1202 on GitHub (Feb 6, 2026). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.12.1 ### Cloud or Self Hosted Cloud ### Steps to reproduce - Go to the "Conversation Opener" settings. - Add a new opening question (e.g., "abc"). - (Note: The main opener text field is currently empty as shown in the screenshot). - Observe that the "Save" (儲存) button is disabled/unresponsive. ### ✔️ Expected Behavior The "Save" button should be active and allow me to save the conversation opener settings, or show a clear validation error if a required field is missing. ### ❌ Actual Behavior <img width="665" height="336" alt="Image" src="https://github.com/user-attachments/assets/e7abb6eb-c48f-4dd0-8426-370632d817ed" />
yindo added the 🐞 bug label 2026-02-21 20:15:54 -05:00
yindo closed this issue 2026-02-21 20:15:54 -05:00
yindo commented 2026-02-21 20:15:54 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 6, 2026):

The "Save" button in the Conversation Opener modal is intentionally disabled when the main opener text is empty. This is enforced by validation logic in the codebase, which requires the main opener text to be non-empty before saving is allowed. This behavior was explicitly added and confirmed as intended in a recent update—there are no configuration options or workarounds to bypass this requirement. If you want to allow saving with an empty main opener text, the validation logic would need to be changed in the codebase itself. You can see the relevant implementation and rationale in the merged pull request here.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 6, 2026): <!-- Answer --> The "Save" button in the Conversation Opener modal is intentionally disabled when the main opener text is empty. This is enforced by validation logic in the codebase, which requires the main opener text to be non-empty before saving is allowed. This behavior was explicitly added and confirmed as intended in a recent update—there are no configuration options or workarounds to bypass this requirement. If you want to allow saving with an empty main opener text, the validation logic would need to be changed in the codebase itself. You can see the relevant implementation and rationale in the merged pull request [here](https://github.com/langgenius/dify/pull/27843). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/8e36a592-9a9d-4584-ae21-97f13c29c275?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/8e36a592-9a9d-4584-ae21-97f13c29c275?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/8e36a592-9a9d-4584-ae21-97f13c29c275?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/8e36a592-9a9d-4584-ae21-97f13c29c275?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/8e36a592-9a9d-4584-ae21-97f13c29c275?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/8e36a592-9a9d-4584-ae21-97f13c29c275?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/8e36a592-9a9d-4584-ae21-97f13c29c275?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20%22Save%22%20button%20in%20the%20Conversation%20Opener%20modal%20is%20intentionally%20disabled%20when%20the%20main%20opener%20text%20is%20empty.%20This%20is%20enforced%20by%20validation%20logic%20in%20the%20codebase%2C%20which%20requires%20the%20main%20opener%20text%20to%20be%20non-empty%20before%20saving%20is%20allowed.%20This%20behavior%20was%20explicitly%20added%20and%20confirmed%20as%20intended%20in%20a%20recent%20update%E2%80%94there%20are%20no%20configuration%20options%20or%20workarounds%20to%20bypass%20this%20requirement.%20If%20you%20want%20to%20allow%20saving%20with%20an%20empty%20main%20opener%20text%2C%20the%20validation%20logic%20would%20need%20to%20be%20changed%20in%20the%20codebase%20itself.%20You%20can%20see%20the%20relevant%20implementation%20and%20rationale%20in%20the%20merged%20pull%20request%20%5Bhere%5D%28https%3A//github.com/langgenius/dify/pull/27843%29.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/32080)
yindo commented 2026-02-21 20:15:54 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 6, 2026):

This is required

Image
@crazywoola commented on GitHub (Feb 6, 2026): This is required <img width="1224" height="558" alt="Image" src="https://github.com/user-attachments/assets/8447da36-592b-453a-9f72-3d268796cd39" />
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#22132
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?