Custom Post Type fields not showing in Dynamic Text dropdown

1

Hi,

I’m having an issue where the fields for a Custom Post Type (CPT) are not appearing in the Dynamic Data dropdown menu when I try to insert dynamic content (such as post title, excerpt, etc.) into elements like headings or text blocks.

Here is the situation and what I’ve already configured:

  1. CPT Registration: The CPT (servicio) is registered via PHP in my child theme with all the required parameters enabled, including:

    • 'public' => true

    • 'publicly_queryable' => true

    • 'show_in_rest' => true

  2. Bricks Settings: I have already enabled this CPT under Bricks > Settings > Post Types.

  3. Permalinks: Permalinks have been flushed and set to %postname%.

  4. REST API: The REST API endpoint for the CPT is accessible and returning data correctly.

Despite these configurations, when editing a layout/template and opening the Select Dynamic Data picker on a text or heading element inside (or outside) a Query Loop, the CPT fields do not show up in the options list.

Could you please advise if there is an additional step or cache/hook required for Bricks to properly index these CPT fields in the Dynamic Data picker?

Environment details:

  • Bricks Version: 2.3.9

  • WordPress Version: 7.0.2

  • PHP Version: 8.3

Thanks.

2

Hi Jonathan,
Welcome to the forum!

I don’t know which fields you’re missing, but for the default CPT data, use the regular post dynamic tags such as {post_title}, {post_excerpt}, {post_url}, and {featured_image}. These are not shown as separate tags per custom post type.

For plain WordPress custom fields, Bricks lists existing post meta keys from the database in the Custom Fields group. Please check Bricks > Settings > Builder and make sure “Disable WordPress custom fields in dropdown” is not enabled. Also make sure at least one post has saved values for those meta keys.

CleanShot 2026-07-27 at 14.13.34@2x
CleanShot 2026-07-27 at 14.13.34@2x2164×640 114 KB

You can also type the tag manually as {cf_your_field_key}. If the meta key starts with an underscore, use the cf_ prefix as well, for example {cf__job_location}.