UnitedCardists.com - The forum for Cardistry, Magic, Custom Decks and All Things Playing Cards.

First, having all past saved ordered lists totally lost may render this feature less desirable to existing users in having to start over. Which was a major bummer.

However, trying to now order them again doesn't seem to be saving. When I switch views it goes back to the same prior order on coming back to custom order.

In addition, the problem of only seeing 8-12 decks on a page at a time, or even at 32 if you use the zoom out function of browser, makes this feature near impossible to use. This is because to drag a SINGLE deck from the bottom to the top takes a very long time in a collection of more than say 50 and near impossible to re-arrange the entire thing. Having a view that allows for more decks on the page is CRITICAL to this feature. That is after it actually working and saving.

This is probably my biggest issue with the site. At 1400+ decks now, not being able to sort them easily and in the way that I like is extremely frustrating.

I'm having this issue as well. Here is what I've found (hopefully it will help to identify and resolve the issue):

For the decks initially loaded in the DOM (looks to be the first 20 decks regardless of "view" type), when using the "middleGrid" view, if you change the order of decks, the new order will be maintained. If you change the order of any of the decks loaded after the initial DOM is created, the ordering changes will not be maintained.

The POST response to "/collection/reorder" returns the same JSON data in either scenario above. I did notice that the highest "weight" return value is a string where all other "weight" return values are integers.

One other thing I noticed is that in the POST request to "/collection/reorder" has the initially loaded 20 decks with an order id that is not the same as the deck's id (i.e. Gemini Noctis has a deck id of 4709 for viewing, etc. but in the POST request is has an order id of 223153). However, the decks loaded after the initial DOM build use the same order id and deck id (i.e. Requiem Autumn is identified as 804 for both id's).

If you change the "view" type, even the original DOM will not maintain ordering changes.

robcan0630 wrote:I'm having this issue as well.

Just wanted to give a huge shout out to robocan who actually did just fix the issue this past weekend. Woohoo! If you guys find yourself having trouble saving just send a message on FB or e-mail me but this issue I think we can officially close out.

Yes, this should be corrected for Collections, Tradelists, and Wishlists when using custom ordering.

I didn't even realize this was being corrected. That makes me happy!

It seems that it doesn't save a new custom order again. It always switches back to my old order since the alphabetical order was fixed.

Harvonsgard wrote:It seems that it doesn't save a new custom order again. It always switches back to my old order since the alphabetical order was fixed.

The problem I had with custom order is that it would repeat some decks and not show others. I only use the newly added sorting and that one seems to work good.

Sent from my S10+ using Tapatalk

Breaking the custom order when fixing the alphabetical order was not my intent. Working on it now. Should be able to get it fixed tonight (I hope).

STLBluesNut wrote:

Harvonsgard wrote:It seems that it doesn't save a new custom order again. It always switches back to my old order since the alphabetical order was fixed.

The problem I had with custom order is that it would repeat some decks and not show others. I only use the newly added sorting and that one seems to work good.

Sent from my S10+ using Tapatalk

That was actually a combination of issues, and the repeating decks should now be corrected. Hopefully I'll have the custom sorting fixed shortly and all will be good again.

Sorry for the trouble, but the all the sort types (custom, alpha, and newest) should now be working for collections, tradelists, and wishlists. Let me know if you are still having any issues.

Thank you for you work on this project. It is appreciated by many, even if unsaid. Thank you.

Sent from my S10+ using Tapatalk

STLBluesNut wrote:Thank you for you work on this project. It is appreciated by many, even if unsaid. Thank you.

Sent from my S10+ using Tapatalk

Thanks, I appreciate your appreciation.