Using Bricks

When Bricks Builder is active, VX fields appear in the Bricks dynamic data picker, and VX lists can drive Bricks query loops. Nothing needs to be turned on; the integration loads automatically when Bricks is present.

VX adds:

• Dynamic tags: one {vx_…} tag per field, with sensible output for images and choices, and filters for formatting.
• Query loops: loop over a repeater, a gallery or related entries, one item at a time.

Everything else stays in Bricks. Use Bricks conditions to show or hide elements; VX's visibility rules are a block editor feature. Values are edited in wp-admin on the post, term or user, never on the Bricks canvas.

Tags are different from block editor tags

Bricks has its own tag syntax, {vx_tagline}. The block editor's VX Script tags, such as @post(tagline), don't work in Bricks, and Bricks tags don't work in blocks. The formatting options are similar, but written as Bricks filters.

After you change a fieldset

Reload the Bricks builder to see new or renamed fields in the tag list.

Technical details for LLMs

• Loads when Bricks is the active theme or parent theme, or Bricks is otherwise loaded (vxframework_bricks_is_available()).
• VX hides Bricks' {cf_…} custom-field tags for meta keys VX manages (vxframework_bricks_managed_meta_keys()), so raw JSON meta isn't bound by mistake. Core post fields (title, excerpt, featured image) stay on Bricks' native tags.
• Password fields have no tags.