Edit Usercard badge on mobile goes to a mostly blank page
-
Edit Usercard badge on my tablet goes to a mostly blank page with the left sidebar and nothing else. No usercard badge picker or anything else.
INB4 "if it's not an iPad then we don't give a shit if our forum fails on it"
*Nevermind, it just takes like 20 seconds to load, and since there's no indication that it's ever going to respond I gave up too quick.
-
How long are you waiting? We did find that it has a delay depending on the number of badges you have. And I don't mean "unique" badges, just total badge count.
And it does have a really long delay even on iPad.
-
Yeah, I end up having to wait about 7-10 seconds.
-
hell, 8 second delay on my desktop.
Good thing they have all the spinner... wait how did a page escape their "spinner all of the things that have waits" philosophy??
-
oh, i know how.
http://what.thedailywtf.com/user-badges/darkmatter.json?_=1428801673861
lmao. Maaaaaaaaaaaaaybe try just requesting a different feed with unique badges only to build that menu plox, @sam?
-
t/1000 claims another victim.
-
oh, i know how.
http://what.thedailywtf.com/user-badges/darkmatter.json?_=1428801673861
lmao. Maaaaaaaaaaaaaybe try just requesting a different feed with unique badges only to build that menu plox, @sam?
Maybe try throwing a DISTINCT into that select statement? Just a thought.
-
I think it's the same feed they use to display your badge list, so they'd need to create a different feed to populate what needs to be distinct dropdowns.
They should also find a way to speed up that original query too, 8 - 12s to pull a couple thousand rows is pretty slow.
-
I believe when I was touching the code there I said... "Eh, the client can do the sorting and grouping."
Perhaps that should be changed to sorting only?
-
Perhaps that should be changed to sorting only?
No, the client side grouping works just fine. It literally takes 12s for the server to return the results according to the network logging.
-
Yes.... and sql-side grouping would fix that?
-
Yes.... and sql-side grouping would fix that?
Only if it speeds up the query that is almost certainly the cause of 99% of the delay. It surely does not take 12 seconds for the server to read a couple thousand rows or to create & transmit 97KB (compressed, 1.3MB unpacked) of json. Only adding a grouping to the existing query probably won't speed up the query all on its own.