Content Search: pagination state causes "no results" when second search returns fewer results than current page
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem Statement
Content > Search pagination retains the previous search's page number when a new search is run, causing a false "no results found" state if the new search returns fewer results than the retained page would contain.
Steps to Reproduce
https://drive.google.com/file/d/1znv2sSMC6P5JC5XD4GrYaIStIQ6v77q6/view?usp=drive_link
Steps to Reproduce
- Under Content > Search, run a search that returns multiple pages of results.
- Navigate to page 5 (or any page after page 1).
- Run a second search that returns some results, but fewer than a full page.
Acceptance Criteria
Expected: Results reset to page 1, showing the new search's results.
Actual: No results are shown, even though matches exist.
dotCMS Version
26.07.06-3
Severity
Medium - Some functionality impacted
Links
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 in the Content > Search interface and reproduce the issue by searching, moving to page 5, then submitting a query with fewer results. Trace where the pagination state is retained or updated when the query changes. Done means a new search always displays from page 1 and shows its available matches instead of a false empty state.
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
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 66/100