100 in the topic cache is fine. But I would raise the Users Unread Post list to a higher number. Certainly higher than the count of topics being shown in the widget.
OK done.
I am now on:
Cache = 200
Users Unread Posts = 100
No immediate effect, will wait a fey days with new posts coming in and then report again
One other thing you should bear in mind as well. Each of your users is going to see a unique list from the recent posts widget depending on what they have already read. The list is generated for each user on a personal basis so what you see is not necessarily going to be what each of your users sees.
I cant confirm that. We shouldnt mix the recent post Widget with the list of unread posts.
The Widget is unaffected if I have read a post or not and it is fine as it is.
The only issue here is, that the Widget doesnt show the number of entries it is supposed to.
The recent post widget list itself is identical to every user and that is fine.
Yellow Swordfish said So – another question or two. On the forum admin > Options > New Post Handling panel what are the settings for number of new posts in the Post/Topic cache? And what is the default setting for the unread posts list for users?
They already are 200 and 50 respectively.
Well then maybe I have another plugin 😉
All I can say is very simple by empirical evidence:
Logged in with my Admin User the Recent Post Widget (RPW) shows 30 entries as of this moment. I have opened and read most of this posts, so those are not in my “Unread post list” anymore.
Logged in with an alternate normal Member Userid I have for testing purposes – without having read any post at all – I have exactly the same 30 entries displayed via RPW!
Not being logged in at all as a third test and looking at the headlines of the RPW list – without even being able to open them – I have still exactly the same 30 entries.
And all this is perfectly fine and exactly how the widget should work because the RPW is not the Unread-Post List.
The only problem is, that 30 are shown and that number is fluctuating and not 50 as set in the options.
But again, maybe we talk about different plugins here. I talk about the RPW as part of “Template Tags and Widgets”
okay, thing all are getting confused…
@yellow-swordfish are you sure you meant the recent posts widget when you said that in post #18?? The recent posts widget doesnt have anything to do with read or unread… its not user based either… the X number recent posts will be displayed to all users and guests (assuming all can view the posts of course – only permissions may change what users see)…
still think folks are mixing recent posts widget and the unread post list (which is user based)…
but hey, I just got back from week in Hawaii so could be not reading straight yet… 🙂
Mr Papa said still think folks are mixing recent posts widget and the unread post list (which is user based)…
I’m talking specifically for the widget. Check the pictures I uploaded on post 12.
but hey, I just got back from week in Hawaii so could be not reading straight yet… 🙂
I envy you! 
actually that question was directed at @yellow-swordfish I was reading that he thought the recent post widget display was user specific and showed unread (which is incorrect)…
took a quick look and I guess I have to ask, are you sure? I cannot replicate it on test site or here…
however, I can say that it appears to be style much different than in tablet and desktop… instead of the dividing line, you get a bunch of spacing after a grouping… so it looks like there is one missing, but I dont think there is…
also, by default (not sure why frankly) the mobile template displays less items than we do by default on desktop… the default count for desktop/tablet is 20 items… in reboot, for phones, that is changed to 15 (maybe due to real estate?)… so check your count and see if you have 15…
you can of course, change the number displayed… or remove the extra spacing there…
@mr-papa – I spent too long looking at the sp_listview_populate_newposts() function. We could probably avoid calling that for the widget if we don’t care whether the post is unread or not.
well, that function is used to mark the unread (theoretically) as read or not… but doesnt affect whether displayed or not… not even sure we show the marker, so yeah, might not need it…
