Allow/Disallow of Like/Dislike at the content level

Thanks you using the module and raising this issue.

Done some major fixes around like & dislikes within 2.2.0 → release,
Have a check if this issue still exist with 2.2.0 → version?

Please check for the module page → for the features covered.

This is a nice to have feature, Will need to implement this feature.

Here's expected feature:

1. Create a data holder to capture the boolean value of Allow/Disallow of Like/Dislike.
2. While creating content, editor/admin role users will have option to Allow/Disallow of Like/Dislike.
3. Based on the selection of Allow/Disallow of Like/Dislike, If TRUE then show Like/Dislike on the template else don't show Like/Dislike on the template.

(Updated the issue desc)

Implemented the Allow/Disallow of Like/Dislike at the content level.

If a particular content is selected with "Disable Like/Dislike for this content?" then the Like/Dislike will not show up.
(refer the screenshot of field widget changes)

We have introduced a data holder for capturing the value of Disable at content level, there is change in the field storage, We have a hook_update_N written which will update all the fields within your site to add Disable data holder. (Note: User data related to likes and dislikes is restored upon the hook update)
You need to run the database updates upon this change (drush updb).

Additional changes done
1. Cleanup of the code with unused code.
2. A minor bug, where one Like or Dislike of Anonymous user was captured, this issue fixed along current feature.

This feature will be provided in the upcoming release.

Thank you all :)

Released this feature in 2.4.0 → version.

Note: Use the latest version of the module & Please check for the module page → for the features covered.

Automatically closed - issue fixed for 2 weeks with no activity.