What works
Sites built on Advanced Custom Fields usually have theme templates that read ACF fields. PageForge works next to that setup, but it fills page content, not ACF fields. Here is what you can rely on today:
- PageForge writes each row into the page’s title, content, excerpt and SEO fields, and keeps the full row with the page.
- The
[pageforge var="Price" fallback="Call for a quote"]shortcode prints a row value on a generated page anywhere WordPress runs shortcodes while showing that page, such as the page content, a widget, or a theme area that runs shortcodes. - ACF field groups can target Pages, Posts or the PageForge content type, so you can add fields to generated pages and fill them in afterwards.
Set it up
- Decide which values change per page and put them in the CSV and template content.
- Use
{Column}placeholders in the template, or the[pageforge var="Column"]shortcode where a placeholder cannot be typed. - Keep ACF for fields that you fill in by hand after generation, or that are the same on every page.
- Generate a few drafts and check every theme area that reads ACF fields.
Limits and notes
- PageForge does not read ACF fields as data and does not write CSV columns into ACF fields, including repeater and flexible content fields.
- ACF values saved on the base layout are not copied to generated pages.
- A theme template that is built only from ACF fields will show those fields empty on generated pages until they are filled.
- ACF text fields do not run shortcodes by default, so the shortcode will not work inside them.
The status is Beta because PageForge has no ACF field mapping. Treat ACF as something that runs alongside PageForge for now.
