Hello, I hope I am posting this in the correct spot. I am unable to update the number of items i see on a page at one time. I am usually able to update it to 50, however there is no longer an option and I can only see 10 at a time. This is happening on both the desktop version and app. Any help would be appreciated!
Will look into it. Maybe we should freeze at 25. Would that be a good number?
honestly, the larger the number the better. i am trying to delete a large number of collectibles from my list, and it’s pretty cumbersome to only be able to do 10 at a time. it would be nice to be able to do 50 again, but i’ll be grateful for whatever you can do! thank you for the reply.
Just a helpful tip, once they update to put the button back where you can change how many you can view, you can actually manually change it to a larger number even as large as your entire collection. Once you click to change the view to let’s say 25 for example, the page will reload and you’ll see 25 collectibles on your screen. You can actually go to the URL bar and find where “25” is on the actual web page address, and change that number to 500. Press enter and the page will populate with 500 or however many you change that number to. I’ve had the same issue where I wanted to update a larger group of items all at once at found that this worked. Of course you’ll have to wait until they put the button back but once they do this should save you a lot of time.
1 Like
The secret is out… Please do not more than 500 items as it taxes the server (it will also take quite some time and the page might just time out and die).
i never even thought of that! thank you! 
i promise to play nice. i don’t want to mess anything up for others.
So for now it is 25. If that works well we will up to 50. Hope that is a little better.
thank you for the help!
I hate to bring this back up after a few months but this definitely needs to be changed back to a varying button or at least a higher number per page, I just had someone ask me what’s the best way to bulk delete a collection without fully deleting their account and I really didn’t have a good option for them because the feature to see 100 per page was gone.
It’s 25 per page now and maybe we can go to 50. We could also build a “Mark All” but not sure how important this is (why does she/he want to delete all her or his items? Is not really a very common case and we got plenty of other stuff that we are working on). They can reach out to support and we delete items for them (if it is all that is relatively easy and we can do that).
Do you know if there are any plans to up it to 50? My use case isn’t bulk deletion; I don’t like scrolling to the bottom to go to the next page. For consideration, maybe options of 10, 25, and 50 items displayed as a toggle and moving the page navigation bar to the top? Thanks for your consideration!
It would have been nice if there was a “Mark All” option. I am going to re-inventory my collection so I created a couple of lists and wanted to move all of the items in HobbyDB into a list called “Not Confirmed”, and then move them to a “Confirmed” list once I have confirmed I still have that item. At the end of inventorying, anything left in the Not Confirmed list would be deleted. Having to do all of this a page of 25 at a time is really frustrating, especially since there is “Batch Actions” button that only applies to the current page and not the entirety of items in the current filter.
As a software developer, I am curious how 500 items taxes your servers? Please don’t tell me you are using Excel as a database? I am joking of course but I have dealt with returning tens of thousands of records and displaying them in grid/table format and never experienced terrible problems (other than speed) until we got over 40K records and most of that was due to the grid control we used and its rendering. I also wouldn’t say that any of our web or SQL servers were all that powerful. Is this more of a datacenter issue?
The site is based on Rails and the component used is Active Admin. The problem is a combination of rendering time (it can take quite some time to render the items) and refresh (as it takes longer that users expect they click the refresh button sending another slow query and then doing so again and again). We should evaluate to go to 50 and I added that into the dev queue.