I see the last two shows I’ve added. if I add another, the last gets pushed out and the first moves over and the new episode takes first placement. This just started today, and I didn’t change any settings. A friend of mine has the same issue with his server. Since the dashboard configuration has been removed from the settings window, there is no way to adjust the “how many or to what date” of recently added shows to display. Please help!
I’m getting the exact result on my PLEX setup. Recently added is showing only three items. Would be nive to have the Dashboard settings back…
Same issue here only seeing 2 shows on the recently added television dashboard no matter how much i add to the library using version 0.9.16.4
The new Web UI will only lists the shows for the first 50 episodes, so if you just added a show with 40 new episodes and the next show has 10 or more new episodes, only these 2 shows will be listed. If you add 50 new episodes from 50 different shows, all 50 will appear. This limit is only for the Dashboard. If you go into the library and set the filter or sort order, all episodes and all shows will be listed.
@MovieFan.Plex said:
The new Web UI will only lists the shows for the first 50 episodes, so if you just added a show with 40 new episodes and the next show has 10 or more new episodes, only these 2 shows will be listed. If you add 50 new episodes from 50 different shows, all 50 will appear. This limit is only for the Dashboard. If you go into the library and set the filter or sort order, all episodes and all shows will be listed.
Would there maybe a way for us to set that limit manually? or even better, have the limit be set by number or shows regardless of numbers of episodes?
Same issue here. It doest just happen in the new Web UI, the other plex apps (ios, android and samsung) report the same way
My friends and family are complaining. They use the recently added television section on the dashboard to see which new episodes have been added that day. Now, If I add a classic TV shows with with a few seasons, then that is all they see, and they don’t see the recently added episodes of new shows, that were previously added the same day.
This seems to be something new, and is not just effecting the web client. It’s effecting all clients.
Why is it now limited to 50 episodes? I don’t believe it was limited like this, before. Could this be made to be configurable?
@MovieFan.Plex said:
The new Web UI will only lists the shows for the first 50 episodes, so if you just added a show with 40 new episodes and the next show has 10 or more new episodes, only these 2 shows will be listed. If you add 50 new episodes from 50 different shows, all 50 will appear. This limit is only for the Dashboard. If you go into the library and set the filter or sort order, all episodes and all shows will be listed.
I’ve been pointed to this topic because I’ve had my fair share of issues with recently added:
They are changing something, implementing something, setting limitations none of this info can be found in release notes.
Why there is a limit? I want 100 or maybe more. Often I add files in batches (ripped kid content) and then what I should just accept that the feature you are pushing so hard on all client is going to be messed?
@planejumper said:
My friends and family are complaining. They use the recently added television section on the dashboard to see which new episodes have been added that day. Now, If I add a classic TV shows with with a few seasons, then that is all they see, and they don’t see the recently added episodes of new shows, that were previously added the same day.This seems to be something new, and is not just effecting the web client. It’s effecting all clients.
Why is it now limited to 50 episodes? I don’t believe it was limited like this, before. Could this be made to be configurable?
Exactly. 50 seems like a reasonable number, but it needs to be shows, not episodes. Combine the episodes into a series, show the available episodes for that series, and let us see all of the Recently Added TV shows, up to fifty. Assuming that we all want to watch the 50 episodes of “Leave it To Beaver” I just ripped and have no interest in anything else is a bad decision.
If anyone is interested, I added a feature request here since it is not specific to a particular client and appears to be universal. Give it a like so that the devs can re-consider changing the logic for this decision.
https://forums.plex.tv/discussion/215330/recently-added-for-tv-give-us-more-shows-in-recently-added-dashboard
I’m sorry but what there to reconsider? I have 107 movies in recently added so what’s wrong with tv shows? There was no such limit in previous versions.
@MovieFan.Plex
It’s not only new web that shows 50 items. It’s across all clients
@“Bartlomiej Baraniec” maybe I misread, your post, or you misread mine. I agree with you 100%. I’m asking the developers to re-consider THEIR decision on how Recently added TV works and displays on all clients now. 
@leelynds what I meant is that I hope that it will be just reverted to previous iteration or simply fixed without any need to reconsider anything. There are many subject on forum showing that this feature is broken right now.
Plex people, Isn’t this easily solved with a GROUP BY clause in your SQL query that generates this view? Just group it by show. This looks really broken. Matching broken functionality from other clients is going the wrong direction.
@honkdazzle you don’t know enough Sql or coding in general if you think that is the solution. To do it in one call, be able to group the resulting data into sets, and show the most recent episode if there was no sets; they’d have to just query a number (how many would probably be dependant on speed) of items, then reduce that number by matching a similar metric (seasons, show).
Yep… I have a few large servers and needed to migrate some TV to another server which blew out all the “Recently Added Television” from the past few days and replaced it with one single thumbnail of the series I moved there. This is a new behavior which made me come look here for a solution. Im guessing this one wont be fixed any time soon with this new server and API rollout. I liked the old setup myself which was stable for the longest time. Ill admit that it looks nice and I sure do appreciate the endless hours of coding guys:) They say change is inevitable right? I mean I have a full archive of the old server RPM’s and can roll back the servers, but Im guessing the updated client devices would have a problem communicating properly with old server s/w. Lets hope this can be sorted out easily.
@random.server said:
@honkdazzle you don’t know enough Sql or coding in general if you think that is the solution. To do it in one call, be able to group the resulting data into sets, and show the most recent episode if there was no sets; they’d have to just query a number (how many would probably be dependant on speed) of items, then reduce that number by matching a similar metric (seasons, show).
Ha. The irony of your post is just, wow.
Go open the sqlite3 database for plex and run this query (or similar to match your TV library section) which is (a) instant, and (b) does exactly what you just said was impossible.
select count(1) as num_items,max(created_at) as last_created_at, parent_id from metadata_items where parent_id not null and library_section_id=2 and metadata_type = 4 and created_at > datetime(‘now’, ‘-7 days’) group by parent_id order by last_created_at desc
You’ll get the last week worth of added episodes, sorted in reverse chronological order (on latest episode added), and identified by season ID and number of episodes added. You could go further and join on the parent’s metadata table to pull in that additional info, but it’d be cleaner to just make separate queries for the ancillary bits. You could also throw a LIMIT 8 on there or however many items they want to show on the dash.
The point is that this sort of bucketization and sorting is extremely easy to do in SQL so clearly someone “[doesn’t] know enough Sql”
All that said, I really doubt this is a performance issue at all. I think maybe someone picked an arbitrary number and that was it. If it was in fact chosen for that reason I recommend staff let the DB handle it with a similar query
Edit: Just noticed the new aggregation bucketizes by series now, not season (nice!), so here’s an updated query that bucketizes by series ID rather than season ID. This looks 100% correct against my library. Runtime is 34ms on a metadata_items table of 45k rows.
select count(1) as num_items, max(i.created_at) as last_created_at, ss.parent_id as series_id from metadata_items i join metadata_items ss on ss.id=i.parent_id where i.parent_id not null and i.library_section_id=2 and i.metadata_type=4 and i.created_at > datetime(‘now’, ‘-7 days’) group by series_id order by last_created_at desc
Yes a list of recently added shows can be obtained fairly easily as shown above. However, the info needed is more than just the name of the shows. What is needed is basically the metadata_items table joined to the media_parts table and to the media_items table that would be IN the query you just made limited to the top say 20 shows. Then PMS needs to convert that to an XML output and transmit that to the client. So it’s not just an SQL issue. So right now, the xml will contain the info for at most 50 episodes. If this was based on show, and say you added the show The Simpsons which has over 600 episodes, the xml would contain the info for all 600 episodes, since all 600 episodes were “Recently Added”. If you added a couple of big shows like this, the XML would be huge.
So some additional logic to limiting the results needs to be added. Just raising the limit doesn’t really solve this problem either as you would run into the same issue using The Simpson’s example and it would be the only show shown even with a limit of 500.
Stop p1ssing about with things that have worked for years perfectly well, there’s is no logic to the ‘improvements’ that Plex Inc have been introducing lately, where is this going to end?
Regards
Plex is moving towards the “Discover” interface in all of their apps. I happen to like that idea. And I think the people I share with like it too, because they can find new things on the server they didn’t know were there.
But how in the world can having only one poster in Recently Added TV, regardless if it is 50 episodes or 600, even remotely be considered as “Discover” new media? One poster says to me, “nothing to see here, move along, come back later”
However, if I go directly to the TV library and filter by recently aired, I get shows all the way back to Dec 15, 1964. On my server that is about 3000 episodes. Works the same on all apps that I have, and doesn’t take an extremely long time to load. Surely the same or similar XML info mentioned above is generated for those 3000 episodes. If I recall correctly, “Recently Aired” used to be limited to 200 episodes. So now we have one bigger page with more items, and one that can quickly become dysfunctional if you happen to add a complete season of one TV show.
To paraphrase @NedtheNerd , it seems you are fixing something that didn’t seem broken to most of us.
@MovieFan.Plex said:
Yes a list of recently added shows can be obtained fairly easily as shown above. However, the info needed is more than just the name of the shows. What is needed is basically the metadata_items table joined to the media_parts table and to the media_items table that would be IN the query you just made limited to the top say 20 shows. Then PMS needs to convert that to an XML output and transmit that to the client. So it’s not just an SQL issue. So right now, the xml will contain the info for at most 50 episodes. If this was based on show, and say you added the show The Simpsons which has over 600 episodes, the xml would contain the info for all 600 episodes, since all 600 episodes were “Recently Added”. If you added a couple of big shows like this, the XML would be huge.So some additional logic to limiting the results needs to be added. Just raising the limit doesn’t really solve this problem either as you would run into the same issue using The Simpson’s example and it would be the only show shown even with a limit of 500.
Looks like you didn’t read or run either query. It isn’t just raising the limit. It’s not retrieving a list of episodes. It’s a different concept. The query generates only what is necessary for the view. Your Simpsons example would work fine. It would be a single row with the Simpsons’ top level series ID and an episode count. It does all the processing for you except pulling the image metadata which is inappropriate. That doesn’t need to happen in the same query. Put a limit 8 on the end (or however many you want for the web or app view) and you’re done. You have a list of metadata item IDs to work with. It’s trivial to add another join though if you must make a hyper specific query (you shouldn’t). It’d be better to use this (and other queries generating view info) to build a single big multi getter run once per page for all the metadata pieces
