Reply to thread

You're right, moderators shouldn't bypass the value match requirements. In my case I'm just playing with a default custom field, Facebook. This requires basically an alphanumeric value (with dots allowed). It already had a valid value in (from my testing before) and I just tried to edit it again with some characters that aren't allowed, e.g. !@#$% and I got an appropriate error.


What you've described doesn't sound like it should be able to happen. The behaviour sort of sounds similar to if the validation is via HTML5 patterns. These would prevent the form being submitted at all, but an error would be displayed next to the field itself. If you're not seeing anything there, then it could be something blocking the request entirely. If you have any fields which are related to advertising then ad blocking software could totally prevent the request from going through. If you have an adblocker enabled, at least, definitely worth trying to disable it to see if the issue persists.


Back
Top Bottom