Coin reference order doesn't work properly anymore [solved]

Since a few days ago, when the reference you're ordering by (with a *) is not the first listed reference, the coin isn't placed correctly in order anymore. It shows up at the bottom instead of its actual position by the reference number. It worked in the past.

Here are a couple example links using Lippe:

Reference Jaeg 7 NW:

https://en.numista.com/catalogue/index.php?e=lippe_earldom&r=&st=1-2&cat=y&im1=&im2=&ru=&ie=&ca=1546&no=*&v=&cu=&a=&dg=&i=&b=&m=&f=&t=&t2=&w=&mt=&u=&g=&c=&wi=&sw=

Reference KM:

https://en.numista.com/catalogue/index.php?e=lippe_earldom&r=&st=1-2&cat=y&im1=&im2=&ru=&ie=&ca=3&no=*&v=&cu=&a=&dg=&i=&b=&m=&f=&t=&t2=&w=&mt=&u=&g=&c=&wi=&sw=

Now it's completely broken. Looks like half the results are gone and I don't see a pattern at all. For example, you can't find this coin anymore by searching for the reference number.

N#570304

https://en.numista.com/catalogue/index.php?e=coree_du_nord&r=&st=147-150-149&cat=y&im1=&im2=&ru=&ie=&ca=3&no=891&v=&cu=&a=&dg=&i=&b=&m=&f=&t=&t2=&w=&mt=&u=&g=&c=&wi=&sw=

It's impossible to search properly now. I hope this gets a high priority…

The Numista catalog is in a bad state. See https://en.numista.com/forum/topic175536.html#p1332003 .

Hopefully they will tell is when everything is working again so we can check to see if problems like this have gone away.

Hello, this is fixed.

I don't understand why that was ever closed. It is NOT fixed.

https://en.numista.com/catalogue/index.php?e=coree_du_nord&r=sung+portrait&st=147-150-149&cat=y&im1=&im2=&ru=&ie=&ca=3&no=*&v=1&cu=&a=&dg=2004&i=&b=&m=&f=&t=&t2=&w=&mt=&u=&c=&wi=&sw=

They should be ordered the other way around.

Sorry, it was only partly fixed. Now it should be fully correct.

References in the date field are sometimes listed first when they should be listed last. Can this be fixed?

KennyG

References in the date field are sometimes listed first when they should be listed last. Can this be fixed?

Could you provide some specific examples?

This link that was provided in the thread earlier is a great example

https://en.numista.com/catalogue/index.php?e=lippe_earldom&r=&st=1-2&cat=y&im1=&im2=&ru=&ie=&ca=3&no=*&v=&cu=&a=&dg=&i=&b=&m=&f=&t=&t2=&w=&mt=&u=&g=&c=&wi=&sw=

KennyG

This link that was provided in the thread earlier is a great example

 

https://en.numista.com/catalogue/index.php?e=lippe_earldom&r=&st=1-2&cat=y&im1=&im2=&ru=&ie=&ca=3&no=*&v=&cu=&a=&dg=&i=&b=&m=&f=&t=&t2=&w=&mt=&u=&g=&c=&wi=&sw=

That link doesn't specify the the sort order. When I opened it in my normal context it sorted by date. When I opened it in a private window it sorted by face value.

And when I specified sort by reference I didn't notice any sorting errors. (Not that I have the focus to check all 113 results without skipping some.)

N#29901

Page example, the Schlum reference (reference from date field) shows first when AKS should appear first (reference from type field)

KennyG

N#29901

 

Page example, the Schlum reference (reference from date field) shows first when AKS should appear first (reference from type field)

The bug reported here is about the order of items in search result, which was what I was talking about in my previous responses. I apologize for the confusion.

I don't recall any previous discussion on where the date field references we supposed to show up in the References list in the Features box.