UNA CMS Version: 14
Module: Comments/Reactions (Studio > Navigation > Systems > Comments)
Environment: VPS (Linux/PHP 8.x/MySQL), production community site
Bug Description:
When reactions are disabled in Studio > Navigation > Systems > Comments (or All Comments), then re-enabled, the system creates duplicate entries in the reactions database table (likely sys_comments_reactions or bx_vote_reactions).
Additionally, the frontend only displays/reads the first 3 reactions from the table, ignoring any beyond that—regardless of actual votes/reactions present.
Steps to Reproduce:
- Go to Studio > Navigation > Systems > Comments
- Disable reactions for Comments (or All Comments)
- Save & clear cache
- Re-enable reactions for the same
- Save & check DB: Duplicates appear for the same reaction types (e.g., multiple thumbs-up entries per comment_id)
- Frontend: Only first 3 reactions show (hardcoded LIMIT 3 suspected)
Database Impact:
text
-- Example duplicates found (pseudocode):
SELECT * FROM sys_comments_reactions WHERE comment_id = X;
-- Returns 6+ identical rows instead of unique (content_id, reaction_id, author_id)
Not Serialization-Related: This is a separate issue from the known BxDolVoteReactions.php BxDolVoteReactions.php unserialize() errors—purely toggle-induced duplicates + display limit.
Request:
- Confirm if this is known & provide patch (code/DB fix)
- Exact table name for reactions on comments?
- Why LIMIT 3 hardcoded? Can we override?
- SQL to clean duplicates + prevent future?
Site Context: Multi-residential community platform (live production). Need quick resolution.
Priority: Medium-High (affects user engagement on comments/posts).
Regards, Chris
Well done Chris I hope we get some answers to this one
@Clubhouse thanks for the support... anyone else missing out on this amazing feature that could have disappeared, never to know.
How serious is caching, cause I would like to know that why the system will read cahced data where the ObjectReaction field is empty. This also contribute to it being read incorrectly.
I've mentioned that whoever plays with it for the first, and not being focused enough will not even know it was a feature added to the comment field box next to Reply...And if not really a lover of reading makes it worse, cause configurating these variable rather appear to be complex so to speak, cause we have timeline as a module and the enabling of this is set in the studio settings panel.
For those who wonder, here are some visuals of the comment navigation types and how we experience it in our unacms system.