\r\n\r\nAs stated here\r\n\r\n- https://github.com/kodadot/nft-gallery/issues/3808\r\n\r\nwe will be turning off 005 & 006 \r\n\r\nCheck if everything works without 006 \r\n\r\nhttps://github.com/kodadot/nft-gallery/blob/3cfbd90799ace8e40af11f24899570ff5017aaff/utils/constants.ts#L34\r\n\r\n- https://github.com/kodadot/nft-gallery/pull/3884",[2061,2062,2063],{"name":1999,"color":2000},{"name":2016,"color":2017},{"name":2033,"color":2003},3813,"Deorbitting rubick-005 & rubick-006","2022-09-02T10:04:40Z","https://github.com/kodadot/nft-gallery/issues/3813",0.7505791,{"description":2070,"labels":2071,"number":2082,"owner":1985,"repository":2005,"state":2006,"title":2083,"updated_at":2084,"url":2085,"score":2086},"//edit:\r\n\r\nsort still needs fine tuning, while the conflicting params don't get passed in at once anymore, it still seems that the sort is not executing correctly (i.e. if you sort for price and then recently interacted, it takes the first argument but not the second one)\r\n\r\n~It seems that on beta, with the newest changes, we lost sort. Currently, picking one of the sort options just adds the parameters to the URL i.e.: https://beta.kodadot.xyz/rmrk/explore?page=1&tab=GALLERY&sort=BLOCK_NUMBER_DESC&sort=UPDATED_AT_ASC&sort=UPDATED_AT_DESC~\r\n\r\n\r\n",[2072,2075,2076,2079],{"name":2073,"color":2074},"bug","d73a4a",{"name":1999,"color":2000},{"name":2077,"color":2078},"p1","D93F0B",{"name":2080,"color":2081},"🧙♀️ - bug-hunt","DC2653",3266,"sort in gallery broken","2022-07-18T13:20:28Z","https://github.com/kodadot/nft-gallery/issues/3266",0.7543639,{"description":2088,"labels":2089,"number":2094,"owner":1985,"repository":2005,"state":2006,"title":2095,"updated_at":2096,"url":2097,"score":2098},"- Blocked by #2327\r\n- check series and spotlight\r\n\r\nWhen I click on Price it puts first 4 0.00 as first and then it goes desc.. it's string/bignum issue?\r\n\r\n\r\n\r\nScore, unique items and unique collections could not be sorted hmm, I recall @roiLeo was looking on this one?\r\n\r\n\r\n_Originally posted by @yangwao in https://github.com/kodadot/nft-gallery/issues/2316#issuecomment-1035167663_",[2090,2091,2092,2093],{"name":1999,"color":2000},{"name":2031,"color":2017},{"name":2048,"color":2049},{"name":2051,"color":2003},2337,"Adjust sorting to be descending at first click v2","2022-03-24T11:05:16Z","https://github.com/kodadot/nft-gallery/issues/2337",0.75488156,{"description":2100,"labels":2101,"number":2108,"owner":1985,"repository":2005,"state":2006,"title":2109,"updated_at":2110,"url":2111,"score":2112},"Right now I would like to sort by long time no interaction and sort it from the most expensive.\r\n\r\n### adjust existing filter names \r\nNew First -> Recently Created\r\nOld first -> Oldest\r\nLast interacted -> Recently Interacted\r\nLong time no interaction -> Unpopular\r\nFrom most expensive -> Price: High to Low\r\nFrom cheaper -> Price: Low to High\r\n\r\n### Spec\r\n- Add recently listed for sale\r\n- It would require writing a new resolver to https://github.com/kodadot/rubick\r\n\r\n\r\n\r\n\r\n\r\n### Ref\r\n- probably ideation to add **min - max** -> https://github.com/kodadot/nft-gallery/issues/2110",[2102,2104,2105,2106],{"name":2103,"color":2000},"$$",{"name":2031,"color":2017},{"name":2033,"color":2003},{"name":2107,"color":2003},"A-search",842,"Ability to sort by multiple metrics","2023-04-03T12:56:50Z","https://github.com/kodadot/nft-gallery/issues/842",0.7556913,{"description":2114,"labels":2115,"number":2118,"owner":1985,"repository":2005,"state":2006,"title":2119,"updated_at":2120,"url":2121,"score":2122},"One final boss mitigated, another appears \r\n\r\nClose when it goes back?\r\n\r\n\r\n",[2116,2117],{"name":2077,"color":2078},{"name":2033,"color":2003},4601,"Rubick down 500 ","2023-01-04T17:51:57Z","https://github.com/kodadot/nft-gallery/issues/4601",0.7633108,["Reactive",2124],{},["Set"],["ShallowReactive",2127],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"wyPUKLPGlghIlnmlEz4i5bCt66R1S6IURU6Y8TRShtQ":-1},"/kodadot/nft-gallery/1848"]