Shortcodes

Every shortcode the two plugins register — including the three that Pro takes over from the free plugin, and which handler actually answers.

Intermediate
5 min read
Applies to 2.0

Authentication forms

Shortcode	Renders	Registered by
`[attributes_login_form]`	the sign-in form	free plugin
`[attributes_register_form]`	the registration form	both — Pro answers
`[attributes_lost_form]`	the lost-password form	both — Pro answers
`[attributes_reset_form]`	the password reset form	both — Pro answers
`[attrua_multistep_register]`	multi-step registration	Pro

Three of these are registered twice, once by each plugin. WordPress lets the later registration replace the earlier one, and Pro loads after the free plugin, so Pro's handler is the one that runs whenever Pro is active. That is intended: the Pro form is the free form plus the extra fields and checks. Your page does not need to change, and it falls back to the free version by itself if Pro is deactivated.

Member area

These render the flows built in the Form Builder.

Shortcode	Flow
`[attributes_account]`	Account
`[attributes_profile]`	Profile
`[attributes_dashboard]`	Dashboard
`[attributes_settings]`	Settings
`[attributes_onboarding]`	Onboarding

A flow in draft renders nothing here for ordinary members — administrators see it with a badge saying so.

Widgets

Shortcode	Renders
`[attributes_login_widget]`	a compact sign-in block
`[attributes_registration_widget]`	a compact registration block
`[attributes_lost_password_widget]`	a compact lost-password block
`[attributes_reset_password_widget]`	a compact reset block
`[attributes_profile_widget]`	a compact profile block

The widget versions are for sidebars and footers — narrower, fewer labels. Use the full shortcodes for a page whose job is that form.

Blocks

Five of these are also available as blocks in the editor, so an editor need not type a shortcode at all. Reach for the shortcodes when you are placing something from a template, a page builder, or code.

Placing a form in a template

echo do_shortcode( '[attributes_login_form]' );

Rendering an authentication form inside a template you also cache will cache its nonce. Exclude those pages from full-page caching, or the first visitor's token is served to everyone and every submission is refused.

Something missing or out of date? Tell support.