Support

Account

Home Forums Gutenberg Fields showing on all Pages despite Field Group location rules.

Solved

Fields showing on all Pages despite Field Group location rules.

  • I have Field Groups set with Location Rules (certain custom post types, on the homepage), but everything still shows up on all pages (albeit as blank sections with only the heading + collapse arrow). I am using the latest WordPress, ACF and Gutenberg (no Beta versions on anything).

    Deactivating Gutenberg and activating Classic Editor fixes the problem.

    Field Group Example – https://cl.ly/47c9b49262af
    Home Page Admin – https://cl.ly/de0460ac0885
    Blank Page Admin – https://cl.ly/306a80ff1f41

  • I just observed this same issue on our main website which relies heavily on Gutenberg. Definitely ignores ACF post type rules when Gutenberg is activated. If I keep Gutenberg activated but also activate Classic Editor, problem goes away (but I don’t get all the editor goodness of Gutenberg).

    • John O

    • November 13, 2018 at 11:19 am

    It looks like this might be the same issue / related to this thread:
    https://support.advancedcustomfields.com/forums/topic/field-group-title-appearing-everywhere/

    If it is, ACF have reported that it will be fixed in v5.8.

  • Yes, that is the issue I’m seeing. Glad to know a fix is on the way.

  • Seems fixed in 5.8-beta2 😉

  • Are those betas available anywhere for download/installation? I’ve got clients giving me some serious stink-eye about the mess in admin right as they’re smack in the middle of populating content for the launch of their new website, and I’d sure like to resolve this for them ASAP if possible.

    Cheers

    Edit: figured out that they’re available through the account screen (I’d previously looked at the github repo to no avail).

  • I’ve now tested 5.8-beta3, and it does fix the issue for me as well. Whew!

    Thanks ACF team for tackling that!

  • I’m experiencing this issue in 5.8.0, after updating to 5.8.1 it still persists.

  • We’ve been experiencing this problem since the release of Gutenberg as well. Weirdly, it has persisted despite our having installed and activated Classic Editor, and no version up to 5.8.1 has fixed it either.

    (Note: Our WP is a multi-site/network installation, and Classic Editor is network activated rather than activated individually per site. Not sure if this would make any difference, but since it’s an unusual configuration I figured it was worth mentioning.)

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.

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 Cookie Policy. If you continue to use this site, you consent to our use of cookies.