Exclude original poster from view counter possible?
Quote from Lou van Wijhe on February 16, 2018, 6:40 amWhen I add a topic, I sometimes edit it a number of times before I get it right. In the beginning I was excited because my new topic had already been viewed say 10 times until I realised it was only me… 🙁
When I add a topic, I sometimes edit it a number of times before I get it right. In the beginning I was excited because my new topic had already been viewed say 10 times until I realised it was only me… 🙁
Quote from Asgaros on February 17, 2018, 9:51 pmHello @lou-van-wijhe
Yes, I know this problem. But its also a little bit hard to find a way to solve this. The same behavior holds when you post an answer into a topic and you edit it multiple times. The view-counter now makes you think that already a lot of people could have seen it.
But I cannot just exclude all content-creators from the view-counter because at some point it would be possible that all active users have answered inside a post and suddenly no views would be counted anymore – while at the same time users still answer to each other. You see, this makes things really complicated and confusing – also from an implementation point-of-view which brings the need to do a lot of checks when a user visits a topic (performance).
So I guess the current simple solution is the best one for the moment. 🙁
Hello @lou-van-wijhe
Yes, I know this problem. But its also a little bit hard to find a way to solve this. The same behavior holds when you post an answer into a topic and you edit it multiple times. The view-counter now makes you think that already a lot of people could have seen it.
But I cannot just exclude all content-creators from the view-counter because at some point it would be possible that all active users have answered inside a post and suddenly no views would be counted anymore – while at the same time users still answer to each other. You see, this makes things really complicated and confusing – also from an implementation point-of-view which brings the need to do a lot of checks when a user visits a topic (performance).
So I guess the current simple solution is the best one for the moment. 🙁
Quote from Lou van Wijhe on February 18, 2018, 4:35 pmThanks for responding! It’s not a big problem but I thought the solution would be easier than it appears to be in practice.
Thanks for responding! It’s not a big problem but I thought the solution would be easier than it appears to be in practice.