This is in the web interface using Chrome.
I set collections to show the content alongside the collections.
I created about 70-80 collections.
The collections work fine.
When I go into the full movie list the letters on the right no longer go to the correct place.
If I click “S” I am placed in the middle of the “Rs”
If I click “W” I end up in the “Ts”
Virtually no letter places me where I want to go.
There are a few other little irritations but I will post about them another time.
That’s an odd one. Seems like the collections are causing a correct offset, but the selection letters are using the non-collection count. I’ll bring it up internally.
And just to be sure, you are using the hosted web app, correct?
@kegobeer-plex said:
And just to be sure, you are using the hosted web app, correct?
I guess I am. I have never really understood what other web app there is. I am using the app you get to by accessing app.plex.tv/web/app I believe that is the hosted web app, right?
@kegobeer-plex said:
That’s an odd one. Seems like the collections are causing a correct offset, but the selection letters are using the non-collection count. I’ll bring it up internally.
You are probably correct. The further I go in the alphabet the greater the error. The “#” and “A” are close to or absolutely correct but by the time I get to “C” the error is obvious.
Edit: If I change the display options to “Hide collection contents” the error is much much more obvious.
Yes, going to app.plex.tv is the hosted web app.
It’s a known bug with the web app, they are already working on it.
@kegobeer-plex said:
It’s a known bug with the web app, they are already working on it.
Thanks. I do not use the letters often so it is not too bad and when I do it is easy to simply use a higher letter to get to pretty much where I want to be.
I wish all bugs were this easy to get around.
I can confirm this (4K monitor). There seams to be some kind of offset.
@mm98 said:
I can confirm this (4K monitor). There seams to be some kind of offset.
No confirmation needed. It’s a known issue.
Just checked and also does it for the Plex App in Android. Can’t comment on the rest
@kegobeer-plex said:
It’s a known bug with the web app, they are already working on it.
It appears that many/most devices that display collections while browsing movies have this bug. Plex has known about the BUG since sometime in December or before and it still has not been addressed.
This is about as major as a bug can get that does not actually prevent use or crash the app.
I expected Plex to have fixed this by now because it seems that it is a fairly simple counting bug where all that needs to be done is adjusting the counting/sorting to take into account the presence of collections where you count the library items plus collections or you count the items that are not in collections plus collections depending or the collection display choice.
But my expectations for Plex to fix this pretty easy to fix BUG is too high. This seems, again, to be a “feature” that will remain unfinished while Plex works to load us down with more and more features while ignoring bugs in the existing ones.
Sigh
@Elijah_Baley
While I have my own problems with Plex developers not always acting fast when they should, your attitude towards them is too negative for my taste. Depending on how “counting” is implemented (items inside a library) and in how wide-spread the counting mechanism is being used within the client and/or server code, this can be a tricky thing to fix.
Obviously, each item now (depending on the view state) needs a a database entry value in a table whether it counts or not. This Needs to be adjusted dynamically, if the user decides to change the way that collections get displayed. If they add a “per collection”-based view state, it gets even more complex. Obviously, using the old way of calculating off-sets in A-Z indices is also not longer that easy. It now depends on how many items are visible/invisble inside the range from # to XYZ.
For the user, this seems an easy thing, but it can easily become very tricky. Give them some time to overhaul the counting mechanisms to take care for even more complex scenarii.
They say that they are working on that… don’t beat them up for not being able to work withing your own time frame.
