-
Using formulator to create a user registration form, all fields properly mapped in formulator. Settings in WP to allow users registration, applied to NOMAD theme subscriber overlay. The form appears correctly and all aspects of the field and registration work correctly.
EXCEPT.
I have the username and PW set as optional and for the fields to only show when drop down menu for MEMBERSHIP is selected. Tested and works correctly. I have the field set not to show if drop down selects GUEST. All field “settings” all fields “mapped” correct. Cache cleared on page, site and browswer. All aspects work correctly so long as I have inserted a username. However, when tested in real time, the form fails if USERID is blank (even though field is optional) Message received: The username can not be empty.
I have added placeholders, default values ([email protected]) and continue to receive the message.
I have deleted the username field and turned off WP anyone can register, cleared cache and refreshed. Message continues to occur. Goolge AI says error is in a generatepress setting that is unspecified.I have browsed through the documentation, and forums for generatepress and cannot find the solution.
-
Hello,
The “The username cannot be empty” message comes from WordPress core, not from GeneratePress. WordPress requires every user to have a non-empty username at the database level, so a registration form can’t truly make that field optional — the form plugin (Formulator) has to either collect a username or generate one automatically before handing the registration off to WordPress. That’s also why the error persists even after hiding or deleting the field: something in the form’s config is still passing an empty username to WordPress.
Whatever AI tool pointed you at “a GeneratePress setting” was mistaken — there’s no GP setting that governs registration validation.
Since the field logic and validation live entirely in Formulator, I’d recommend reaching out to their support team for how to handle an optional/auto-generated username.
-
Problem resolved. Even though Formintor fields are all mapped properly, I manually added a new meta map to user registration username that simply duplicated the existing fields in Forminator. Noting that existing fields in forminator must remain in tact as well. Redundant. But it works
-
Ok, glad you got it working!
- You must be logged in to reply to this topic.