dotCMS / dotCMS/core

[DEFECT] Content Drive breadcrumb link does not preserve query parameters

Open
#33,800 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

dotCMS: Chrome Redesign Team : Falcon
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Problem Statement

The breadcrumb navigation in the content detail/edit view (e.g., Content > Content Drive > [Item]) fails to preserve the state of the "Content Drive" when clicking to return. Currently, clicking the "Content Drive" link in the breadcrumb sends the user back to the root view of Content Drive, losing all previous navigation context, such as expanded folders and any applied filters (by type, status, search, etc.).

https://github.com/user-attachments/assets/83ae4aba-1e14-4603-8035-0e34a43ebb22

Steps to Reproduce
  • Navigate to Content > Content Drive.
  • Apply one or more filters. For example, expand a folder (e.g., /blog/).
  • Optional: Apply additional filters (e.g., filter by content type).
  • Click on a content item (e.g., Blog details) to open its edit or detail view.
  • Observe the breadcrumb, which now shows: Content > Content Drive > [Item Name].
  • Click the "Content Drive" link in the breadcrumb.
Acceptance Criteria
  • When navigating from a content item view back to "Content Drive" using the breadcrumb, the state of filters and expanded folders must be preserved.
  • The "Content Drive" breadcrumb link (URL) must be dynamically constructed to include the necessary query parameters (like path and other filters) that reflect the previous view's state.
Proposed Solution

To resolve this, the "Content Drive" breadcrumb link should capture and include all active query parameters from the Content Drive list view (e.g., path, search terms, and other filters) so that clicking it returns the user to the correct, filtered state.

dotCMS Version

latest

Severity

Critical - System unusable

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the flow from Content > Content Drive to a content item’s edit or detail view, then inspect how the Content Drive breadcrumb link is built. Confirm that returning through the breadcrumb preserves the expanded folder, path, search, and other active filter query parameters.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.