Troubleshooting

1. Reactions do not appear on the entity

Issues:

• The entity page shows no reactions at all.

Fixes:

• Check the field is enabled on the entity's "Manage display" page.
• Check the role has the "View reactions for field …" permission - for anonymous visitors, the Anonymous user role needs it too.
• Check reactions were not set to "Hidden" for that specific entity while editing it.

2. Reactions are visible but cannot be clicked

Issues:

• Reactions and counts render, but the radios are disabled.

Fixes:

• Grant the role the "React to field …" permission, and "Modify reactions for field …" if users should be able to change their reaction afterwards.
• Check the reaction status of the entity is "Open", not "Closed".

3. Reaction counts are outdated or not updating

Issues:

• Anonymous visitors see stale counts, or counts never change.

Fixes:

• Reaction changes invalidate the cache tags of the voted entity - if counts lag for anonymous visitors, make sure reverse proxies and CDNs respect Drupal cache tags.
• Check the vote result calculation schedule in the Voting API settings (/admin/config/search/votingapi). With "on cron", results only update when cron runs.

4. An anonymous visitor can react again after returning

Issues:

• The same anonymous visitor can post multiple reactions on the same content.

Fixes:

• Review the "Anonymous detection method" field setting: cookie detection is per browser, IP detection covers everyone behind the same IP.
• Review the "Anonymous vote rollover" window - after it passes, a returning visitor is treated as new by design.

General tips

• Clear Drupal caches after changing field, display, or vote type settings.
• Review Reports → Recent log messages for errors.
• Keep Voting API Reaction and Voting API updated to their latest releases.
• If an issue persists, search or report it in the issue queue.