Bricks Builder offers powerful dynamic data features that pull content from custom fields and post meta.
These dynamic fields should display real content from the database on both editor and frontend.
But sometimes the dynamic data appears correctly in the Bricks Builder editor interface.
The live frontend shows empty spaces or placeholder text instead of the actual dynamic content.
This problem makes dynamic data useless for displaying custom fields and ACF data on the website.
Why Bricks Builder dynamic data fails on the frontend
Bricks Builder fetches dynamic data from the WordPress database using REST API requests.
If the REST API is blocked or slow to respond, dynamic data may not load on the frontend.
Caching plugins may cache pages before dynamic data has been fully loaded from the database.
The custom field key name may be misspelled or may not exist for the current post or page.
ACF or other custom field plugins may not be active on the current website installation.
How to check if dynamic data is configured correctly
Edit the page in Bricks Builder and click on the element that uses dynamic data.
Navigate to the content settings and look for the dynamic data configuration panel.
Check that the data source type (post meta, ACF, etc.) is selected correctly for the field.
Verify that the meta key name matches exactly what exists in the WordPress database.
Test the dynamic data by adding a test value directly to see if it displays properly.
Step by step guide to fixing Bricks Builder dynamic data
Follow these steps to ensure dynamic data displays correctly on the Bricks Builder frontend.
- Check that the custom field or ACF field actually contains data for the current post
- Verify that the meta key name is spelled exactly correctly (case-sensitive)
- Ensure that ACF or other custom field plugins are active on the website
- Clear all caches including plugin cache, CDN cache, and browser cache completely
- Check that the WordPress REST API is accessible by visiting /wp-json/ on the website
- Disable all caching plugins temporarily to test if they interfere with dynamic data
- Test dynamic data on a default WordPress theme to check for theme conflicts
- Update Bricks Builder to the latest version available from the official website
- Regenerate Bricks Builder CSS from the settings panel after making any changes
- Contact Bricks Builder support with specific details about which dynamic data is failing
How to test if dynamic data is being fetched correctly
Open browser developer tools and navigate to the Network tab for the website page.
Reload the frontend page and look for REST API requests in the network log information.
Check for requests to /wp-json/bricks/v1/ or /wp-json/acf/ endpoints on the page.
Click on these requests to see if they return the expected dynamic data from the database.
If requests return empty data, the problem is with the data source or REST API configuration.
Bricks Builder dynamic data troubleshooting reference table
Here is a reference table for diagnosing dynamic data problems in Bricks Builder.
| Symptom | Most likely cause | Recommended solution |
|---|---|---|
| Dynamic data works in editor but not frontend | Caching plugin serving stale version | Clear all caches and exclude dynamic pages from caching |
| Dynamic data empty everywhere | Meta key name misspelled or missing data | Verify meta key and check database for values |
| Some dynamic fields work but others do not | Specific field type not supported | Check Bricks Builder documentation for supported field types |
| Dynamic data shows raw shortcode instead of value | Shortcode not being parsed | Use dynamic data field instead of shortcode |
| Dynamic data appears but is outdated | Cached version of dynamic content | Clear object cache and disable caching for dynamic content |
For more information about Bricks Builder dynamic data, visit the Bricks Builder page on wpwizzy.com.
Preventing Bricks Builder dynamic data problems in the future
Always verify custom field names before adding dynamic data to Bricks Builder elements.
Use the same meta key naming conventions across all custom fields for consistency.
Clear all caches after adding or updating any dynamic data on the website pages.
Test dynamic data on a staging website before deploying to the live production site.
Document all dynamic data connections for future reference and troubleshooting needs.
Keep ACF and other custom field plugins updated to their latest versions regularly.