web_registration_form Shortcode
The web_registration_form shortcode renders an invitation registration form using the same output and protected submission flow as Registration Form in Gutenberg. WooCommerce must be active. Rendering never creates an account.
The attributes below match the current Page Builder controls and public output. Use raw syntax only for reviewed content that cannot be maintained through the visual controls.
Usage
[web_registration_form]Attributes
| Attribute | Default | Accepted values | Purpose |
|---|---|---|---|
no_param |
native_form |
native_form, show_error |
Without an invitation, show the WooCommerce account template or the message below. Open registration follows WooCommerce settings. |
message |
— | Passive inline emphasis | Greeting; {email} is the invited email and {username} is the inviter's display name. |
display_email_input |
— | yes |
Display an editable email field. Otherwise the invited address is fixed server-side. |
invalid_invite_link_msg |
— | String unless stated otherwise | Controls the invalid invite link. |
expired_invite_link_msg |
— | String unless stated otherwise | Controls the expired invite link. |
success_msg |
— | String unless stated otherwise | Controls the success message. |
no_param_msg |
— | String unless stated otherwise | Controls the no param message. |
el_id |
— | Valid unique HTML ID | Enter section ID (Note: make sure it is unique and valid according to w3c specification). |
el_class |
— | String unless stated otherwise | If you wish to style particular content element differently, then use this field to add a class name and then refer to it in your css file. |
Verification
Review valid, missing, invalid and used invitations on an uncached staging page. Successful registration creates a standard subscriber (or customer when subscriber is unavailable), consumes the invitation and offers a login link. It never modifies the inviter's site membership. Passwords require 12–4096 characters. Signed-in visitors see My account instead of the form. The empty/expired messages retain their existing defaults; there is no age-based expiration control.
Use one native account fallback per page. Exclude this page from full-page caches/CDNs and clear old cached forms when updating. The native fallback retains WooCommerce hooks and account policies. The invitation branch uses WordPress registration validation and WooCommerce registration-error filters; verify bespoke captcha or account plugins on staging. No public block stylesheet is added; password estimation is conditional.