SOP: display nested ACF fields in Elementor when dynamic tags fail
A diagnosis for a field that exists in WordPress but does not render on the frontend: verify data, identify integration limits, and reuse a safe presentation layer.
The problem
A section built with custom fields displayed dynamic content until it needed to read a subfield inside a group. The data was still stored in WordPress, but Elementor reported that it could not find the subfield. Renaming things blindly would not help because the problem was data structure, not content.
The root cause
ACF fields can live inside groups or repeaters. Some dynamic-tag interfaces cannot resolve nested values using only a subfield name. In addition, if the presentation logic was added directly to a parent theme, a theme update may have replaced it even while the ACF data and configuration remained intact.
The resolution
I first confirmed that the main field and subfield had data. Then I checked whether a shortcode or helper function already existed to read the full group and return the required value. Reusing that layer avoided duplicated logic and allowed an explicit shortcode in the Elementor block.
When no helper exists, the answer is a small function that fetches the group, validates the presence of the subfield, and returns escaped HTML. It should live in a child theme or custom plugin, not in theme files that can be overwritten by an update.
How to validate it
- Save a test value and confirm it exists in the admin area.
- Add the call to a test page before changing the public section.
- Verify the frontend with cache cleared or disabled.
- Test the empty state so it does not print warnings or broken markup.
- Document the group, subfield, and call that render it.
Apply it to similar issues
When a dynamic field does not appear, split the investigation: does the data exist, can the builder read that structure, is there an existing helper, or is cache serving an old version? This sequence avoids rewriting PHP when the issue is configuration and avoids blaming the builder when a theme update removed the logic.
The prevention is straightforward: document custom shortcodes and keep presentation logic out of a parent theme. Fields and the code that displays them will then evolve as a system rather than hidden dependencies.