View Issue Details

IDProjectCategoryView StatusLast Update
0005241OXID eShop (all versions)1.01. Products (product, categories, manufacturer, promotions etc.)public2016-08-12 14:56
Status assignedResolutionopen 
Product Version4.7.3 / 5.0.3 revision 54408 
Target VersionFixed in Version 
Summary0005241: Sorting is saved to session—which is not nice.
DescriptionThe selected sorting is stored in session. This results in practically ignoring default sorting of categories as soon as the user selected a custom sort and this for as long as the session lasts. This might be long and might confuse the user if he accidentally selected a sorting which makes less sense. He cannot "repair" this situation by simply going back to the homepage, start over and click on the category again. He will end up in the same "broken" view. This is unintuitive.
The problem becomes more severe if categories are fundamentally different and therefore require different default sorting. If one selects a sorting in one category, it is automatically applied to all other pages—nevertheless if it actually makes sense or not.

In our opinion it would make more sense to pass the selected sorting on as a GET-Parameter. This is also the only REST-ful way of implementing sorting, while the current solution does not respect this standard.
Right now one cannot share a link to a list-page with another customer if the former one selected another sorting. The receiver won't see the same articles, since the sorting is not transferred as part of the URL. Following the REST-theory this should be the case. Everybody should see the same content under the same URL.
This becomes also relevant when bookmarking pages for later, sharing pages on Facebook/Twitter and so on and so forth.

Would be nice to see this fixed.
TagsNo tags attached.
PHP Versionany
Database Versionany


related to 0005631 resolvedLinas Kukulskis Category default sorting leads to empty category lists when switching languages 
related to 0006083 resolvedanton.fedurtsya article sorting fields not verified against valid field from admin settings 
related to 0005839 acknowledged Category default sorting gets saved as user sorting 



2014-05-15 12:42

reporter   ~0009909

Waiting for the PO decision.


2016-08-12 14:21

developer   ~0011730

saving sorting in session makes browser caching impossible and varnish caching more complicated. So using request parameter would make this things much easier.