An interesting thing came up today when a client was testing a newly upgraded site. The original site was on U13 and we’ve moved to 17.2
In U13, when on a node with a list view, you used to be able to click a header and sort the list by the name, sort order, last edited date etc and this would update the url with a query string. This meant if you then opened up an item, you could click back in your browser and the sort order would be remembered, since it was in the url. However, in U17, the url doesn’t get updated and so when you click back, nothing it persisted. You need to sort every time.
The same happens if you search the listview, you used to be able to search, the querystring would be updated and you could navigate within the results, open an item from the results and click back and keep the results from the search. Now you need to search fresh every time.
Has anyone else found this and have you found a work around? Asking here before I open up a issue on Github as I’m guessing this isn’t an easy fix.
Also a bit odd that changing the sortby doesn’t return us to page 1 (if you’ve already moved to another page)
Could the intention have been that opening an item from a collection view should be in the infinite editor panel? Then don’t need to persist state in the url, but would be nice to do both.
Thanks both. Ye, I think what I might do is spin up a U13 site, replicate the behavior and record it again in U17 and raise it as an issue.
It might be that there is a work around or as said, its been an oversight.
Its funny, you think everything is fine but then a user does something totally unexpected
That’s a good observation. You can indeed open it in the infinity editor (and I think that that is the default now?), but there is still the option of opening them directly. And that behaviour is maybe less tested because it’s not the default.
