My ACF fields have somehow moved into the right column under Permalink, etc… How can I move them back into the main body under the Gutenburg blocks like normal?
Pretty sure that’s a Gutenberg problem and not an ACF problem. The block editor wants to put EVERYTHING in that tiny sidebar on the right.
If you create an ACF block and assign the field group to the block, you will at least be able to fill out the fields within the block. If the fields are for a CPT, you can add that block to a block template for the CPT, so that it’s there automatically when you create a new CPT post.
There may be a way to force the field metaboxes to show up below the edit screen, but I’m not aware of it.
> If you create an ACF block and assign the field group to the block, you will at least be able to fill out the fields within the block. If the fields are for a CPT, you can add that block to a block template for the CPT, so that it’s there automatically when you create a new CPT post.
The fields created by ACF blocks are not saved as custom fields, so they’re not post meta. Therefore, this is not necessarily a solution.
A possible solution:
I found changing the position to “High (after title)” ('position' => 'acf_after_title') put the fields back in the main area, below the block editor.
This used to work fine before. So its probably related to a WP update.
However its not a “gutenberg issue” but seems like a conflict (or maybe wordpress removed something?) between gutenber and ACF
Setting it to high didnt sort it for me.
I just had the same issue. It was to do something with the ordering of WordPress meta boxes.
I was recommended by the support team to create a second user account and test with that account. If you can view AFC fields normally in the editor window with the new user account, it is to do with the settings with the old account.
It involves deleting some entries from database entries using phpMyAdmin interface. The recommended I to refer to this article:
https://www.vntweb.co.uk/reset-wordpress-metabox-positions/
It resolved my issue after carefully following the above article.
Best of luck!
