You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And then report a comment as either "Contact Info Strike ..." or "Paysite Strike ...", regardless of what you choose, ContextMod will only match the first rule in sequence for detecting any report, without actually matching the report reason.
With the above rules, anything coming in that's reported will always match the "Contact Info Strike" rule. Even if the report reason is "Paysite Strike ...". If you re-arrange the above rules so Paysite Strike is on top, then all reports will always match the "Paysite Strike" rule and never trigger the "Contact Info Strike" rule.
The text was updated successfully, but these errors were encountered:
ContextMod is not correctly parsing User Report Reasons on comments/submissions
To recreate the issue,
Create a couple basic rule in ContextModerator to leave a Comment based upon a specified report reason that begins with a specific but unique term:
And then report a comment as either "Contact Info Strike ..." or "Paysite Strike ...", regardless of what you choose, ContextMod will only match the first rule in sequence for detecting any report, without actually matching the report reason.
With the above rules, anything coming in that's reported will always match the "Contact Info Strike" rule. Even if the report reason is "Paysite Strike ...". If you re-arrange the above rules so Paysite Strike is on top, then all reports will always match the "Paysite Strike" rule and never trigger the "Contact Info Strike" rule.
The text was updated successfully, but these errors were encountered: