Already in Bricks

Requests Bricks already answers.

Kiln leaves these out because Bricks already does them. Each entry says where to find it.

Some popular requests on the ideas board are already answered by Bricks itself. Kiln doesn't duplicate them. Here is where to find each one in Bricks 2.4.3 (checked 15 October 2026).

You want Where it is in Bricks
A reading progress bar The Reading progress bar element.
A fallback when a dynamic data tag is empty Add @fallback:'text' to the tag, for example {acf_subtitle @fallback:'No subtitle'}, or @fallback-image: for images.
An element only when a URL parameter is set Element conditions > Dynamic data, compare {url_parameter:utm_source} with a value. For a match anywhere in the address, use the Current URL condition.
A loop of the logged-in customer's orders Query type Account : Orders. Turn on Bricks > Settings > WooCommerce > Enable advanced modular elements first (marked Experimental).
A username field on a registration form The Form element's User registration action: Field: User name. Without it, Bricks builds the username from the email address.
A confirm-password field On the second password field of the Form element: Mark as confirmation password. Kiln adds the same for email fields (Form: confirm email field).
Perspective for 3D transforms Style tab > Layout: Perspective and its origin.
Maintenance mode bypass for logged-in roles Bricks > Settings > Maintenance mode > Bypass maintenance: logged-in users with chosen roles.
Single pages that stay public in maintenance mode Bricks > Settings > Maintenance mode > Exclude posts/pages. Kiln adds whole post types, an IP list and a share link.

When Bricks ships a feature that a Kiln module provides, Kiln retires that module and this list grows. Your license keeps covering the rest.

See what each Kiln release adds or retires in the changelog.