Mr Lucky Well-known member May 29, 2018 #1 Affected version 2.0.7 The like list underneath the resources shows two likes as if from deleted members, however when you click for deotails, those two are normal undeleted members
The like list underneath the resources shows two likes as if from deleted members, however when you click for deotails, those two are normal undeleted members
Chris D XenForo developer Staff member Sep 7, 2018 #2 Does this resource still list those as deleted members? If so, could you please provide the following: The value of the like_users field in the xf_rm_resource_update table (there may be multiple records for the same resource) The user IDs of all three of those members who are listed in the "Members who liked this" overlay
Does this resource still list those as deleted members? If so, could you please provide the following: The value of the like_users field in the xf_rm_resource_update table (there may be multiple records for the same resource) The user IDs of all three of those members who are listed in the "Members who liked this" overlay
Mr Lucky Well-known member Sep 7, 2018 #3 Yes Resource = https://cafesaxophone.com/resources/so-you-want-to-join-a-band-and-why-you-should.132/ BLOB - 71 B Likes shown is now slightly different from above screenshot Although it shows three, there are now 4 likes EDIT: hmmm, it’s four, I can’t count! User IDs: 5868,5285,5160,4845 Last edited: Sep 7, 2018
Yes Resource = https://cafesaxophone.com/resources/so-you-want-to-join-a-band-and-why-you-should.132/ BLOB - 71 B Likes shown is now slightly different from above screenshot Although it shows three, there are now 4 likes EDIT: hmmm, it’s four, I can’t count! User IDs: 5868,5285,5160,4845
Mike XenForo developer Staff member Sep 7, 2018 #4 If you like and then unlike the content does it resolve the issue? If so, then it might be hard to handle as it would've been a cache-time issue.
If you like and then unlike the content does it resolve the issue? If so, then it might be hard to handle as it would've been a cache-time issue.