Page builders overview

Mass Custom Fields hands your field values to page builders as dynamic data: you pick a field in the builder's own dynamic content picker and the value is printed where the element sits. Elementor additionally gets widgets, {{ }} variables and display conditions.

What each builder gets

Dynamic data is free for every builder. Builders other than Elementor do not get the widgets. In any builder that renders shortcodes you can also print a field with [wpmcf_field group="…" field="…"] (see Output, formats and escaping).

A builder is picked up automatically when it is active; there is nothing to switch on. Bricks and Divi are themes, so the integrations register once the theme has loaded.

How a field is referred to

A builder stores a field reference made of the field group key and the field key, with an optional path into a Group, Repeater, Flexible content or Clone value:

You do not type these in Elementor or Breakdance: the picker lists "Group › Field" entries. In Bricks you type or pick {wpmcf:product.price}, and the Oxygen shortcode takes the reference in key.

Which fields a builder offers

Only active field groups are listed. Password fields are never offered and never printed, even through a path or a manually typed reference.

What a field prints

Everything is escaped for where it is printed. A text value containing [shortcode] is printed as text and not run; HTML typed into a text field is shown as text.

Which post is read

• On a single post or page, the field comes from that post.
• In a loop (a Bricks query loop, an Elementor Pro loop, the Post grid widget) the field comes from the post of the current loop item.
• Field groups that appear only on an options page are read from the options values and need no post of their own. When the element sits in the content of a post or page, the values print only if that post's author may open the options page (the manage_options capability by default). A page written by a contributor shows an empty value for an options field; the same element on an administrator's page prints it. The wpmcf/options/capabilities filter changes the required capability for a group.
• A value read from another post (a loop item, or an id saved in a widget) is printed only if the visitor could see that post anyway: published and public posts, or posts the logged-in user may read. A draft or private post of someone else, and a password-protected post, give an empty value. This is the same rule as the [wpmcf_field id="…"] shortcode (see Output, formats and escaping); the wpmcf/shortcode/can_view filter changes it.

If something fails

Each builder adapter runs under its own module in the plugin's fault protection. A failure returns an empty value, the page keeps rendering, and the error appears under WPM Fields › Settings › Health. If an adapter fails five times in ten minutes it is switched off until you turn it back on there. See Health and troubleshooting.

Page caches

Values that appear on many pages (options pages, Global Data) clear your page cache when they change, so a builder page does not keep an old value. See Page cache plugins.