Product sort order not respected

Hi all,

Since upgrading a client's site from v2.5 to v3.5, we've noticed that the default sorting of products within each category page is no longer respecting the product's 'Display Order' property.  Since the default 'Display Order' value is 0, several specific products have been set to use negative display order values.  This resulted in them being listed before the other products in the list, but this is no longer the case after the upgrade.

Looking at the code's history, could this have been a bug that was introduced when the default sort option was changed from 'Position' to 'Relevance'?

Thanks,

Nick

Hi Nick,

please check the following setting:

"Configuration -> Settings -> Catalog Settings", Tab "Product lists", Option "Default product sort order"

That should be "Position".

Then perform the manual megaserach indexing and execute task "cache bereinigen".

Regards

Wolfgang

Hi Wolfgang,

I have change the setting to be "Position" and the sort order changed immediately (without needing to clear cache), but it is still not showing them in the correct order.  I have a product (X) with "Display Order" set to -5, and all other products are set to 0, but product X is not the first in the list.

I have also cleared cache (from the main Settings icon in the back-end, and also from Scheduled Tasks -> Clear Cache -> Run Now), but the order remains the same...  Please help!

EDIT:  I have tried to recreate this issue on the demo site, but it will not allow me to change the default category sort order, for security reasons.

Any update on this, guys?  Please can someone attempt to re-create it to confirm that it's a genuine bug?

I have the same problem. Nickh you managed to solve the problem? 

According to the change-log it's a bug that will be fixed in the next version.

Thanks very much for finally accepting that this is an issue!  A bit disappointing to see that it took another person for you to acknowledge this problem though.

Any idea about when the next version is due?

Thanks,

Nick

We need to be able to reproduce a problem in order to fix it. The error only occurs under certain conditions. The next version is planned for the end of this quarter.