[DEFECT] Content Drive does not refresh when switching the 'site' (host) in the top dropdown
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem Statement
Currently, the content listing and folder tree in the Content Drive do not react when the user switches the active 'site' (host) using the dropdown in the top-right corner.
When switching from Site A (e.g., "Testing") to Site B (e.g., "demo.dotcms.com"), the Content Drive view remains unchanged, displaying the content from Site A. This confuses the user, as they expect to see the content associated with Site B.
The root cause appears to be related to the global store not updating correctly, or the Content Drive component not reacting to the store's update after the site change.
https://github.com/user-attachments/assets/90ccf52e-231d-4857-ac08-a9c9935c6521
Steps to Reproduce
1- Log in to dotCMS.
2- Navigate to the Content > Content Drive section.
3- Select a specific site that has unique content (e.g., Site "Testing").
4- Create a File or Folder in that site (e.g "test-folder")
5- Verify that the content for the "Testing" site (including test-folder) is visible.
6- Click the 'sites' (hosts) dropdown in the top-right corner of the screen.
7- Select a different site (e.g., "demo.dotcms.com"), which does not contain the test-folder.
Observe the issue: The Content Drive view (both the left-hand navigation tree and the main listing) does not update. It continues to show the content from the "Testing" site (including test-folder), even though "demo.dotcms.com" is now selected in the dropdown.
Acceptance Criteria
-
Given the user is on the Content Drive screen.
-
When the user changes the active 'site' (host) in the top dropdown (e.g., from "Testing" to "demo.dotcms.com").
-
Then the Content Drive (including the folder tree and content list) must automatically refresh.
-
And the view must display only the content and folders that belong to the newly selected 'site' (host).
dotCMS Version
latest
Severity
Critical - System unusable
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the site switch from Content > Content Drive, comparing the folder tree and content list before and after changing the top-right site dropdown. Trace how the selected site reaches the Content Drive view and its global store. Done means both views refresh and show only content belonging to the newly selected site.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100