Not a bug Outdated Trending Content

[Marcus]

Affected version

2.3 beta 6

On the front page the last trending and closed topic was replied a decade ago.

 

[Jeremy P]

I've mentioned this a few times now but this isn't a bug, those threads have just received a lot of (bot) views in the last seven days. We already give you tools to disable guest view counting, which we've done here now, or exclude views from the score altogether.

 

[bzcomputers]

I've mentioned this a few times now but this isn't a bug, those threads have just received a lot of (bot) views in the last seven days. We already give you tools to disable guest view counting, which we've done here now, or exclude views from the score altogether.

Does this take time? ...because the threads listed in the widget are the same as were there when the issue was reported.

 

[Jeremy P]

Yep, it does not apply retroactively.

 

[Mouth]

Yep, it does not apply retroactively.

Perhaps it should be reset, even by manual DB action, so that it can be demonstrated/shown that this works as desired?

 

[Jeremy P]

I'm not overly concerned with it personally. We can reassess in a week, after which point the score should be derived from views of logged in members only.

 

[PrivatePilot]

We moved servers recently and as a result of better server performance, increased search engine bot traffic has resulted. That's the good news. The bad news is that as a result, this is now happening to us.

One thread that is now being featured has not seen a reply in over 22 years.

I've changed the weighting a little as well as adjusted the half life setting in an attempt to fix this until things level out, but some time later this section doesn't seem to have updated. Is there a way to manually trigger something to update this section?

 

[Jeremy P]

Any changes to the weights or half life should take effect immediately as they invalidate any caches. However disabling guest view counting does not apply retroactively so it can take time before they fall out of the time window. In the meantime you may want to disable view count weighing entirely, or shorten the time window in the per-widget options.

 

[Chromaniac]

changing the logging value seems to take a while at my end as it seems to prune the table in database on the spot. maybe change the logging period to 1 day and keep increasing it daily for a few days

 

[PrivatePilot]

However disabling guest view counting does not apply retroactively so it can take time before they fall out of the time window.

Thanks, this seems to be what is going to be necessary to resolve this now actually as the weighting changes don't seem to having a whole lot of effect. In hindsight it may be increased guest views vs search engines causing this, or whatever is crawling the site now with apparent reckless abandon isn't being identified as a recognized bot. Hmm.

Is there any way to trigger anything in the ACP to speed up any changes disabling guest view counts, perhaps something in ACP>Tools>Rebuild Caches?

 

[Jeremy P]

Unfortunately not, short of disabling the view count weighting and/or lowering the per-widget time window for a few days.

 

[PrivatePilot]

Unfortunately not, short of disabling the view count weighting and/or lowering the per-widget time window for a few days.

Thx, I set the view count rating to zero for the time being and it immediately fixed the issue, with actual current threads now showing up in there.

In the coming days I'll creep the number back up and see what happens. I disabled guest view counts as well, how long should I expect it to take for this to take effect so far as being able to reinstate the view count weighting and only have it weight based on actual logged in users moving forward?

 

[beerForo]

I had the same problem and the solve was; View count: 0

 

[beerForo]

Thx, I set the view count rating to zero for the time being and it immediately fixed the issue, with actual current threads now showing up in there.

I see you did the same thing.

 

[beerForo]

In the coming days I'll creep the number back up

I tried 1 and it still happened, mine stayed at 0.

 

[Jeremy P]

how long should I expect it to take for this to take effect so far as being able to reinstate the view count weighting and only have it weight based on actual logged in users moving forward?

It depends on your widget time limit. If it's set to count views from the last 7 days, then it will take 7 days from the time guest view counts were disabled for them to fall outside of the window. After that it should be safe to count views again.

 

[CedricV]

It depends on your widget time limit. If it's set to count views from the last 7 days, then it will take 7 days from the time guest view counts were disabled for them to fall outside of the window. After that it should be safe to count views again.

Any chance we can choose what forums it takes into consideration in the near future?

 

[beerForo]

I disabled guest view counts as well

Keep in mind this is a global setting and not a widget setting. So a lot of your threads will now have single digit views/0 instead of the bot counts in the hundreds/thousands.

 

[Jeremy P]

Any chance we can choose what forums it takes into consideration in the near future?

As announced in the HYS, we have plans to build out the trending system further over time, and we’ll take the feedback we’ve gotten into account.

However this is an old, closed bug report so not really the place to get into the weeds regarding outstanding suggestions.

 

[CedricV]

K

As announced in the HYS, we have plans to build out the trending system further over time, and we’ll take the feedback we’ve gotten into account.

However this is an old, closed bug report so not really the place to get into the weeds regarding outstanding suggestions.

Apologies.