-
-
Inaccurate View Count Behavior on Topics and Profiles
Will this issue be resolved in version 5.0.6? @Matt @Marc
-
-
-
Inaccurate View Count Behavior on Topics and Profiles
The problem also exists on this forum you can check this thread. On my forum, someone artificially inflated the view count in new threads, making this counting feature useless as it no longer represents any real value.
-
PanSevence started following Inaccurate View Count Behavior on Topics and Profiles
-
Inaccurate View Count Behavior on Topics and Profiles
Hello, We've encountered an issue related to how view counts are handled on topics and user profiles in Invision Community. ProblemEvery time a user refreshes a topic or profile page (e.g., using F5), the view count increases. This occurs even if the same user repeatedly refreshes the page within seconds, from the same IP and session. There appears to be no throttling or cooldown period to prevent view inflation. Test ScriptWe tested this with a simple script in the browser console: let interval = setInterval(() => { location.reload(); }, 10); // Simulates 100 refreshes per secondThe view count continues to increase rapidly with each reload. The behavior is the same on profile pages.
-
Invision Community 5.0.5 Releases
This is a BETA version, why are you updating the production site? That's irresponsible!
-
-
Argument #1 ($name) must be of type string
I'm seeing this error in multiple groups, not just a single one including the guest account. YYou can check it on my site the data in the client panel is up to date.
-
Argument #1 ($name) must be of type string
Any update? @Marc @Matt
-
-
-
Argument #1 ($name) must be of type string
The error occurs across different URLs, not just one specific page So it seems the common factor is the ?_fromLogin=1 parameter, which is present in all cases
-
-
-
-
Invision Community 5.0.5 Releases
https://invisioncommunity.com/forums/topic/482460-problem-with-reactions/
-
Problem with reactions
-
-
Problem with reactions
I had the same issue and created a ticket for it. After the Invision team analyzed it, it turned out that the problem was caused by an outdated translation entry. I updated it to the default language and it started working properly
-
-
-
-
Critical error version 5.0.5 Beta 2, I need help
It works perfectly, thank you for the quick intervention 🙏
-
-
Critical error version 5.0.5 Beta 2, I need help
Hmm, do you think this will also solve my case? When can we expect the final version?
-
Critical error version 5.0.5 Beta 2, I need help
So the issue was indeed reproduced on a clean system? Will the current problems with reactions be fixed?
-
-
Critical error version 5.0.5 Beta 2, I need help
What can I do in this situation?
-
Critical error version 5.0.5 Beta 2, I need help
I'm not entirely sure since when. A few users started reporting this today and I looked into it and it is indeed a big problem. I'm not sure what I can do about this