yes it does…  simple to change ours to say 100 instead of  5 (in our footer) and it goes as far back as needed…

and the db query for this post list (based on list topic class) has no way to limit the date in anyway…  you can limit it by forum, topic or limit (count) but not date… it will get as many entries as it can…

I guess we would have to do some debugging to see what is going on…  but that would likely require ftp access (as well as sp admin access to site) so we could add the debug code…

I see, thanks for your offer. I might come back to this in 1-2 weeks, if I cant nail down the problem by myself.

Having a third person outside my sphere, acting uncontrolled with admin access during Live-Hours in the background, makes me a bit nervous. Don´t take this as personal misstrust, there is none. I would have that reaction, even if Tim Cook himself would offer to debug my code – maybe even more with him, than with you – lol.

Call it technical paranoia resulting from 30 years experience with murphys law. 😉

So I will try to do some additional tests and checks by myself, but might come back to your nice offer as a last resort later.

Thanks again, Hari

nope. no issue… understand fully…

first thing I would do is get a look at the query… then the results…

you could add a filter on sph_topic_list_query to see what db query is (or just dump it out in sp-list-topic-class.php…

then look at the $records that gets returned from the $spdb->select() query in that class…

You can review the sql being used and the data being returned by the query using the data inspector in our toolbox. The widget uses the Topic List View to query and populate the data object.