I've noticed that the article hits counter increases every time a user revisits an article page, even within the same session. This seems to be happening unconditionally without any limitations.
5.4
I'm not entirely sure what the intended behavior should be, but I see a few possibilities:
Once per user lifetime – The counter should increment only once per user for each article, regardless of how many times they visit it (even across different sessions).
Once per session – The counter should increment only once per user session. If the session ends and the same user visits the article again in a new session, it would increment once more.
Current behavior (unlimited) – The counter increments unconditionally every time the article is accessed, even by the same user in the same session. (This could potentially be exploited to artificially inflate hit counts or affect layouts that display popular articles.)
When a user visits an article, the hits counter increments by 1.
If the same user revisits the article multiple times in the same session, the counter continues to increase.
(visit article +1, go back, revisit the same article +1, and so on)
There is no apparent limitation preventing multiple counts from the same user/session.
This also happens at Preview window at the admin panel.
(Preview +1, close, Preview +1, and so on)
No response
I'd appreciate clarification on which behavior is actually intended so I can better understand if this is a bug or working as designed. If it's not intended, I'd be happy to help look into a solution.
Thank you!
| Labels |
Added:
bug
|
||
| Labels |
Added:
No Code Attached Yet
|
||
Why would you expect the article hit count to be restricted to once per user or once per lifetime
Once per user (lifetime for the same user) on the same article would make sense like views on a post on Facebook for example.
There is another possibility that it is designed to increase for the same user, even though, I think it should be limited by something like a session for example.
Otherwise, it is not a good idea to leave an easily incremental element in the layout, If I send multiple requests, I can make many issues. For Example:
Not all of this could happen, but that's what I thought of.
What do you think?
What do you think?
I think you are redefining the meaning of hits
I think you are redefining the meaning of hits
How?
I am not defining it, I am saying the possibilities.
One of them is the "views" as I have just explained.
The other is it's meant to be as it is, if that's it we should limit it by session to make it a little bit considerable
and to avoid it to be easy increasable.
I think you are redefining the meaning of hits
How?
I am not defining it, I am saying the possibilities.
One of them is the "views" as I have just explained.
The other is it's meant to be as it is, if that's it we should limit it by session to make it a little bit considerable
and to avoid it to be easy increasable.
it is working as intended
Thank you for the clarification.
I understand that the current behavior is intentional.
Would the maintainers be open to discussing an optional configuration
(e.g., count hits per session or per user) to prevent artificial inflation?
If this is something acceptable, I would be happy to work on a PR.
The hit counter is a relict from a very early version. It is not a bug - it was intended as it is many years ago - but now it is surely a candidate for improvement (performance).
This should be closed as its not a bug and moved to feature evaluation
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-03-18 13:18:15 |
| Closed_By | ⇒ | CSGoat0 |
Why would you expect the articler hit count to be restricted to once per user or once per lifetime