tuccbtw

Hi Alimir,

Thanks for the quick response.
So, I changed the logging method to logged by username, and here are the observations.

1) I can at least like and unlike now.
2) There are now 2 log entries I can see in the statistics while testing: one is of course when I like a post while being logged in as admin. The second entry is for guest users i.e. any user not logged in but still can like.

3) The issue now at hand is that for the 2nd type of log entries(guest users), I can see only 1 entry and that too against the IP 127.0.0.1. So, If I like a post as a guest user with my wifi IP (guest user only) and again like the same post using my mobile network IP, the net result is 0 likes which otherwise should have been 2.

So, ultimately, the Logged by IP mechanism is not working as it used to work before the update, because when we used logged by IP, the IP and the like/unlike status, was also logged in the statistics for each unique IP address and the likes counter used to work accordingly.

In the current scenario, like/unlike are logged in statistics but they are captured against a single row and with 120.0.0.1 IP. So, there is a gap here. Ideally, it should have different IP addresses logged in statistics based on like and unlikes clicks by different users instead of updating the same row.

For example, in current situation, I only see following line for guest likes. Here ypu can see we have “like”. Once we unlike it the status will change to unlike in the same row with same 127.0.0.1 ip

XXX #Guest User like 1234 ABCArticle July 18, 2020 @ 2:07 pm 127.0.0.1

Previously it used to be like

XXX #Guest User like 1234 ABCArticle July 18, 2020 @ 2:07 pm 127.0.0.1

XXX #Guest User like 1234 ABCArticle July 18, 2020 @ 2:07 pm 11.22.22.44

XXX #Guest User unlike 1234 ABCArticle July 18, 2020 @ 2:07 pm 11.33.22.55

Let me know your thoughts and kindly help.

Regards,
Ayush