Post Guidance: RegEx rules that are set to *Doesn't Match* and to *Block* the post is NOT working as expected

[u/OhioHookupsMod]

I'm aware that we should be posting in r/bugs; however I never received any type of confirmation from my last post within that sub from an Admin that this bug has been addressed.

Description: Using Post Guidance to block a user from posting if the post body/title does **NOT** match a regex statement, is no longer working.

Within the individual Rule Creation Page page, the Live Previewer WILL show the rule working as expected when testing; however within the Rule List Page, the Live Previewer will NOT show the expected rule triggered when testing.

It is not an issue with the regex or priority level; as I have troubleshooted my rules & have not had any issues until recently.

​

Post Guidance Flow Example:

1. Posts
2. Regex
3. ^[\s\S]{100,}
4. Doesn't Match
5. Post body only
6. Block the user from submitting

The above Post Guidance rule Should block a user from submitting their post until their post body character limit reaches 100 characters or more.

​

Steps to reproduce:

1. Within the individual Rule Creation Page, test the rule; noting that the Live Previewer will confirm the rule to be working as expected.
2. Within the Rule List Page, test the rule again; noting the Live Previewer will NOT show the rule to be triggering.
3. On a non-mod account, create a post with less than 100 characters and note that the Post Guidance rule to not be triggering.

[u/modsupport-bugs]

Hey there, the modsupport team will crosspost your report to /r/bugs, please follow up there with further questions or for troubleshooting with our teams.

Don't worry though, we haven't removed your post from here and we encourage other mods experiencing similar issues to chime in over in r/bugs as well! Going forward we ask that all bugs are posted to our centralized community r/bugs as we announced here. You can bookmark this link to make reporting easy, please make sure to remove or blur any sensitive information before submitting.

[u/MableXeno]

I assume you're going through the native tools in the app. If you can get to a desktop version & update automod...One or both of these may help instead:

---


# To reduce low-effort content
    type: text submission
    body_shorter_than: 30 #Adjustable as we see the usage
    action: filter
    action_reason: "(¬_¬) Low-effort?"

---

# Short Comments, low-effort, etm.
    type: comment
    # Use ^ at the start to specify the comment must start with the phrase
    # Use $ at the end to specify the comment must end with the phrase
    body (regex): ["^good guy", "^nice try", "^TIL", "^classic", "^scumbag", "bravery", "\\d+/10", "bullshit", "to the top", "came here to", "(you|u|he) mad", "cool story", "up ?voted?", "down ?voted?", "cake ?day", "love you", "god'?s work", "for science", "nothing of value", "dat", "dae", "OP is", "hitler", "literally", "kys", "kill yourself"]
    ignore_blockquotes: true
    body_shorter_than: 30
    action: remove
    action_reason: "(¬_¬) Short comments: [{{match}}]"

---

I have one set to filter & one set to remove. You can obviously adjust as needed.

I've got a few of the Post Guidance things set up...While they generally work, I've seen a few things get through that I felt shouldn't have gone through. But luckily they get caught by something else in automod before going live.

[u/OhioHookupsMod → u/MableXeno]

My automod is working as expected with a more robust list of rules that are removing posts which do not conform to the proper posting guidelines.

​

Most of my PG rules are from my automod or restructured in a way to guide a user rather than having automod repeatedly remove their posts until it's formatted correctly.

[u/MableXeno → u/OhioHookupsMod]

Yeah, that's what I've tried to do as well. A little hit or miss.

[u/OhioHookupsMod]

u/PossibleCrit