Although we use ACF (Advanced Custom Fields) for creating blocks, under the hood, some actions are not permitted.
Following the latest update of ACF PRO, the company has changed its policy. Now, fields cannot be displayed anywhere in the WordPress menu.
If you require full ACF Pro features, such as:
- Creating fields for Posts and Pages
- Creating Settings Pages
- Creating Custom Posts Types and Taxonomies
You should consider purchasing ACF Pro from their official website.
To align fully with their marketing strategy, we will refer to it as ‘Gutenberg Studio – Scripts Organizer Add-on’ instead of ‘ACF Add-on’.
Managing Custom Fields in Gutenberg Studio.
To access the custom fields, you need to open a block and:
- Click on Preview
- Click on Fields
Once you follow these steps, you will be able to manage fields for your blocks.
Using your own ACF Pro
Gutenberg Studio includes a copy of ACF Pro (version 6.2.2), so blocks work without installing anything else. Because ACF changed its terms, this included copy stays at 6.2.2 and its admin menu stays hidden. We patch it ourselves when security issues come up.
If you install and activate ACF Pro with your own license, Gutenberg Studio detects it and uses your copy instead of the included one. You get the latest ACF version, its full admin menu, and fields for posts, pages, options pages, custom post types and taxonomies.
Your existing blocks and their fields keep working when you switch; nothing needs to be migrated.
The [acf] shortcode
Since version 1.7.5, the [acf] shortcode is turned off while Gutenberg Studio uses its included ACF copy, the same default as current ACF versions.
With your own ACF Pro active, the shortcode follows ACF's own settings.
To turn it back on with the included copy, add this to a code snippet:
add_filter( 'acf/settings/enable_shortcode', '__return_true', 20 );
Shortcode output is escaped, so unsafe HTML such as script tags is removed.