When clicking the **Add File** button on the knowledge base document page, the left sidebar navigation switches to the global main menu of the Dify homepage, instead of retaining the sidebar menu belonging to the knowledge base detail page.
- Dominant language
- TypeScript
- Stars
- 156k
- Forks
- 24.6k
- Avg merge
- 22h 9m
- Merged PRs (30d)
- 610
Description
### 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.17.0
### Cloud or Self Hosted
Self Hosted (Docker)
### Steps to reproduce
When clicking the **Add File** button on the knowledge base document page, the left sidebar navigation switches to the global main menu of the Dify homepage, instead of retaining the sidebar menu belonging to the knowledge base detail page.
### ✔️ Expected Behavior
When opening the Add File modal on the knowledge base detail page, the left sidebar menu should remain the knowledge base detail sidebar instead of switching to the global main navigation menu.
### ❌ Actual Behavior
_No response_
Contributor guide
Research direction
Reproduce the issue on the knowledge base document page in the self-hosted Dify 1.17.0 setup by opening Add File. Trace the Add File modal and the sidebar navigation behavior; done means the knowledge base detail sidebar remains visible instead of switching to the global homepage menu.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 67/100