The two blocks in the editor
Attributes Login Form and Attributes User Page, what each one places, and when a block is the better choice over the shortcode that does the same job.
- Beginner
- 5 min read
- Applies to 2.0
Where to find them
Open a page in the block editor, press +, and type attributes. Two blocks
answer, both under an Attributes category of their own:
- Attributes Login Form — a shield icon, registered as
attrua/form - Attributes User Page — a people icon, registered as
attrua/user-page
The two names in code are what you would put in a theme.json allow-list, a
allowed_block_types_all filter, or a block-pattern definition. The titles are
what the editor shows.
They are Pro. With only the free plugin installed the category does not appear, and the shortcodes are your route.
Attributes Login Form
Places one of the authentication forms. Which one is a setting on the block, not a separate block: pick Login, Register, Lost password, Reset password or Profile from the Form panel in the sidebar.
The panels beneath it change what the form says and how it looks:
| Panel | Controls |
|---|---|
| Form | which form, and where it sends people afterwards |
| Wording | every label, placeholder and button on the chosen form |
| Style | colours, spacing and type, shared with the free plugin's form styling |
Every wording field starts empty, and empty is not a bug. An empty slot means "use whatever the form says for itself", which is the translated string. Filling one pins that text in the language you typed it in, on every visitor's screen. Leave them empty unless you actually want to override the wording.
Attributes User Page
Places one of the four member pages — Account, Profile, Dashboard or Settings — chosen from the Page panel.
It renders by delegating to the same shortcode the Login Page Manager would have
used, so a page built with this block and a page built with [attributes_account]
produce the same thing.
Block or shortcode?
Both routes exist and neither is deprecated. The difference is where the settings live.
| Block | Shortcode | |
|---|---|---|
| Where you set options | sidebar panels, with previews | attributes typed into the shortcode |
| Works in | the block editor | anywhere — classic editor, widgets, page builders, template files |
| Colour and spacing | editor controls | your theme's CSS |
| Survives a theme change | yes | yes |
Use the block when you are already in the block editor and want to see the form while you place it. Use the shortcode when the form has to live somewhere the block editor does not reach — a widget area, an Elementor template, a PHP template in your child theme.
Do not place two authentication forms of the same type on one page. Both the block and the shortcode render a real form with real field names; two of them submit the same names, and the browser has no way to tell which you meant. One form per page, whichever route you took to put it there.
The five widget shortcodes
The block's PHP registers five shortcodes alongside it, which are what the block delegates to and what you would type by hand:
[attributes_login_widget][attributes_registration_widget][attributes_lost_password_widget][attributes_reset_password_widget][attributes_profile_widget]
These are the widget forms — compact, meant for a sidebar. They are not the
same as the full-page [attributes_login_form] and friends described in
your authentication pages.
Something missing or out of date? Tell support.