List Pages Lose Search On Back

bythewiseman · August 13, 2026, 7:42pm

Hello,

Is there a setting in Umbraco to have the child of a list page have a back button to return to the parent page with the search you did still in place?

e.g.

1000 news item
I search for chocolate
It returns 20 pages
I go to page 5
I select a news item
I want to go back but I cannot
And when I hit the browser back button I am back at page 1 with and the search/filter is undone.
And the tree on the left when I am looking at the news item is not indicative of my search.

Or is this a new implementation of Umbraco 17 that won’t change?

bythewiseman · August 13, 2026, 7:54pm

Actually, I just noticed the browser back button takes you back to the tab you last clicked Not back up a level. Man. That’s going to confuse a lot of clients

justin-nevitech · August 13, 2026, 8:18pm

Hi @bythewiseman

If you’re able to confirm how this used to work in v13, it may be worth raising this as a regression if the behaviour has changed in v17.

It does sound like it may confuse a lot of people!

Justin

bythewiseman · August 13, 2026, 8:27pm

For example, my college website:

I search for HNC:

And then select page 7:

And select any course on page 7:

You can see the back button which takes me back to exactly where I was prior to selecting the node. And the node in the tree on the left stays rock solid and doesn’t change as it has been told to be a list view.

But Umbraco 17 wants to show me nodes that have no relevancy to what I am doing (different site in the next thumbnail) :

A lot of extra processing time/power used up to change the tree when there was no need to as it the News node here in this U17 website is has a list view.

We are only a few months away from U13 being EOL, and there is so much I feel is wrong/missing in U17. I know we had to get away from angular for good reasons, but U17 still to me feels like some got a blank sheet of paper and a very basic understanding of Umbraco and tried to re-write it, when U13’s look and feel and functionality was (imho) almost perfect!

bythewiseman · August 13, 2026, 8:29pm

PS I try not to raise too many bugs these days. There are folks that have an idea of how they want U17 and the future of Umbraco to go and they close down issues faster than I can blink these days, saying things like “well it works fine on my machine”. And it has become very disheartening to try to help out.

justin-nevitech · August 13, 2026, 8:52pm

Hi @bythewiseman

If you can recreate this consistently and it’s not related to your custom code or a third-party package, then it definitely sounds like a bug. From a user perspective I would expect the back button to take you back to where you were before, including with filters and pagination preserved.

Definitely raise it.

Justin

bythewiseman · August 13, 2026, 9:12pm

But that’s the thing, the back button has been removed. It’s not a bug. It’s a feature of the new UI to not have a back button, it feels like.

leekelleher · August 14, 2026, 9:50am

To note specifically on returning to a Collection (old List View), we have recently fixed this for the next minor (17.7 / 18.2, out mid-September). It’ll remember the view, filter, ordering and pagination.

github.com/umbraco/Umbraco-CMS

Collections: Remember the view, filter, ordering and page of a collection (closes #22418) (#23571)

v17/dev ← v17/feature/collection-interaction-memory

merged 08:52AM - 13 Aug 26 UTC

madsrasmussen

+1710 -148

**Description** Fixes #22418 Adds interaction memory to collections, mirro…ring the tree. The current view, filter term, ordering and page number are stored when they change and restored when the collection is mounted again, for the rest of the session. The Collection code already had logic to store the selected Collection View in localStorage. That code has now been deprecated and replaced by the interaction memory system. The Documents Mock set has been updated with a collection of 1,000 items. Along the way, I realized that the filter and ordering were not wired up correctly in the mocks, so that has also been fixed in this PR. **How to test** For quick testing, you can use the Documents Mock Set. It has a pre-installed collection of 1,000 items. For real database testing: Set up a Document Type with a Collection configured, allowing a child Document Type beneath it. Create a document of that type and enough children to fill several pages. 1. Open the document's collection tab. Go to a later page, then open another document in the tree and return: the collection opens on the page you left. 2. Set a filter, sort by a column and switch view. Leave and return: each is restored, with the filter field showing the term and the sort arrow on the sorted column. 3. Open a sibling document using the same Document Type: it keeps its own page, filter and ordering rather than inheriting the first one's. 4. Do the same on a root collection — Users, Members, Languages, Relations or Webhooks — where there is no entity unique. 5. Reload the browser: memories are cleared, as with the tree. 6. Media: repeat 1–3 on a Media Type with a Collection configured, and check that the ordering arrow in the table view matches the restored ordering.

With the back button, I’d recommend raising an issue on the tracker. I appreciate that you may feel disheartened, (and I’m not sure which past issues you’re referring to), but I can say that at HQ we definitely take the time to digest all feedback. In the case of Collections, we’ve been iterating on the feature based on community feedback. I’m not saying it’s perfect, but we are listening.