View Full Version : Sorting by Price
Hello,
The sorting by price be it low-high or vice versa doesn't seem to work.
Err.... don't know what else I can say!
Thanks!
Mine's the same - now
I'm sure this used to work!
Hi Guys,
Tried this on ShopWindow.com and seems to be working.
Can I take a look at your sites?
Cheers
Amo
Hi Amo,
www.lotsandlots.co.uk
thanks!
Paul
Confuscius
10-07-07, 08:29
It seems to me that the sort by price function is nearly working! When the sort by price filter is applied then, say, on results 21 to 30 then the results returned are the products that are in fact 21 to 30 in order of price but in most instances they are not kept in sort order within the range of 21 to 30. Results 11 to 20 are less than or equal in value to 21 to 30 and results 31 to 40 are higher or equal in value to 21 to 30. In other words, the block of results returned is correct but their respective order to each other within the block is not.
So results of £21, £22, £23, £24, £25, £26, £27, £28, £29, £30 may end up being displayed as £24, £28, £29, £21, £25, £26, £27, £23, £22, £30 - please try a couple of queries and test if my theory holds true for everything.
I assume that hi-lo exhibits the same behaviour but I have not tested this as yet!
Paul
Try searching for 'television' in all categories or 'electronics' and sure enough it will display televisions, but use 'low high' it will always default to 'television' category, (which is not available in the initial search category). The first 50 pages are 'ZERO' priced products, skip to page 100 and the lowest price is slill £3.99.
Great excuse for buyer to leave and a lot of bloody hard work undone!
I think we underestimate the fact the customers have pre-armed knowledge of the subject they are searching, and that they already know who are the potential competitors for price comparison could be.
We need a 'Shop by Merchant' facility to offer to our visitors!.
......Jake
Paul Inman
12-07-07, 11:33
Hi guys.
Thanks for spotting this error and for your theory Confusius it was spot on. It has been resolved just now.
This bug arose after we made a few back-end changes that restricts the actual dataset that can be returned to 1000 (you may have noticed this in the pagination max range). This will allow us to hold the data in cached indexes.
This change is just one in a number that we are actively working on to help speed things up.
Cheers,
Paul
Very nice.
Much, much better - THANKS
Confuscius
14-07-07, 13:21
Hi Paul
What would be really nice if this limiter was a variable defined at 'our' end so that we could limit the size of the dataset returned - for example, I would love to be able to choose say 20 merchants but limit it to a maximum of 20 results per call - would be a relly nice way to create some 'smaller' sites to play with from an SEO perspective.
Also need to resolve the issue of being able to have Affiliate sub accounts with different Merchant selections.
Please consider for future development!
Paul
we made a few back-end changes that restricts the actual dataset that can be returned to 1000 (you may have noticed this in the pagination max range)
Hmmm....
So that's why half of the pages are vanishing from my site as they fall out of the cache. :( That's a lot of wasted search engine crawls :mad: