❗ Oh well, it was too soon to celebrate. While it does work by removing the post type prefix, it also breaks all page links resulting them in 404. Unfortunately I can’t remove/edit my previous reply.
Looks like now it is possible with the latest ACF (v6.3).
I got the ide from stackoverflow, where @cybmeta suggested to “set the slug argument for your custom post type to ‘/’ when registering the post type”. I did the same with ACF and now it seems like it is working well.
Followup from the support:
It appears that this [bug] is happening because the block editor uses a different API than the Classic Editor, and it does not register meta boxes. Instead, the metabox is registered as a React “Panel”.
Actually, we have this report on our dev team’s issue-tracking list and we’re looking into removing that panel if the “Meta Box” setting is set to “No Meta Box”.
Glad to know you got a fix in the meantime, I’ll be sharing that with the dev team as well.
Hopefully this will have an official fix soon.
IMPORTANT UPDATE [2]:
Good news regarding to my comment here mentioning that the filter “removed other random metaboxes of other plugins”: I can confirm that it was just a bug with the specific plugin (I also reported that to the plugins developer) and it was NOT related to this fix, as I was encountering the problem randomly, even this filter completely removed from the website. So again, this fix solves the original problem without any side effects!
@webdvp: You are welcome, I created this thread for this reason, to help others!
@hube2: I can confirm that there seems to be no issues with this fix. I contacted your dev team to move forward to a fix.
Hi John, thanks for your reply!
What you wrote is working for posts without Gutenberg editor, but it is not working on post with Gutenberg enabled, this was my original problem.
The solution I posted above fixes this issue.
However, IMPORTANT UPDATE:
Although this filter fixed the ACF-Gutenberg meta box hiding issue, I’ve run into other issues caused by this, which answers my question why this code is not implemented. The filter removed other random metaboxes of other plugins which made them unusable, so I think this solution needs more tweaking to work without affecting other things in a bad way.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Privacy Policy. If you continue to use this site, you consent to our use of cookies.