Export the default/global CMS collection as ACF options pages for reusable site-wide Main, Header, and Footer fields.
Where: CMS → options / global fields — Define global fields
Key ideas
- Default collection: The default/global collection is exported to option storage rather than a page or post instance.
- Region routing: Fields attached to header or footer elements are routed to the matching sub-page; other global fields stay under Main Options.
- Shared source of truth: Templates read the same option value wherever the bound global element appears, so editors update it once in WordPress.
Steps
- Create or use the default/global CMS collection and define stable field names and types.
- Bind site-wide header, footer, and general elements to those fields.
- Preview every template that consumes the global values, including missing and long content.
- Publish/export to a WordPress staging site with compatible ACF options-page support.
- Open Theme Settings → Main, Header, and Footer in WordPress, enter representative values, and verify every consuming template before production use.
Generated structure
- A parent Theme Settings options page.
- Main Options for general default-collection fields.
- Header Settings and Footer Settings sub-pages when those regions have fields.
- ACF field groups whose location rule targets the appropriate options-page slug.
When it is generated
The exporter registers options pages only when a default collection exists. Destinations without the required ACF options-page APIs skip that registration rather than creating a broken admin screen.
Limitations and important notes
- The destination must provide compatible ACF options-page APIs.
- Renaming field machine keys after live content exists can orphan or require migration of stored option values.
Troubleshooting
Theme Settings does not appear in WordPress
Confirm the project has a default collection, the export includes its fields, and the destination has the required ACF options-page support enabled.