Hi there, @faxtrot117… what you are doing isn’t working because of this.
You need to do something like get a count of those characters extracted with Regex, and when the count is greater than 0, show an error message or disable the register button.
Just to see it work, put a condition on the register button that makes the button not clickable when a condition that includes the expression in your first screenshot plus :count > 0 is true.
I got that regex from the same thread that you linked to, so something else is probably going on with your setup. You can try inspecting the button element with the debugger to see if you can get a hint that way.
Well, it’s exactly the same as what you are doing except I am making the button not visible instead of not clickable, so I still think there is something else going on with your setup.
The issue is because the interpretation of your pattern is only occurring on one event thus far in this thread: on page load.
Embed your text input in a new group, of type text. Set the initial value of your text input to be the this new parent group’s text. Then on the text input, start a workflow of “when input’s value is changed”, then pipe your regex replace into a set-value to the parent group’s text (parent group’s text = input text’s value: regex replace".
This way you fire your regex replace on the event of the user actually typing, instead of just once on page-load. It will write the parent group’s value, which will in-turn reset the input’s value with the replacement.