Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Marko Heijnen

    (@markoheijnen)

    It seems not if I read https://www.ads-software.com/support/topic/tabify-support-acf-502. It’s not my issue to solve here.

    Thread Starter sireneweb

    (@sireneweb)

    ACF 5 is compatible now with your plugin, i asked an improvement. Now all is ok

    Sireneweb, ACF 4 worked side by side with Tabify until I’ve upgraded to 5.0.2, 3 days ago. No new patch versions have been released yet. So I’m wondering if have you tested it extensively. Are custom fields correctly show per post type in your Tabify settings ?

    Thread Starter sireneweb

    (@sireneweb)

    Yep for me it’s working, did you see all ACF Groups fields in tabify parameters page (options-general.php?page=tabify-edit-screen) ?

    The biggest difference with ACF 4 you see all ACF Groups fields for each custom post in Tabify edit screen

    Yes, in Tabify settings, I see them all no matter which post type I select.
    I think this is the real problem, beacuse it causes Tabify to save wrong data
    (fileds who do not belong to a specific post type are saved as they do).
    Then in edit.php switching tabs breaks everything.

    Since the error seems being not blocking (post save or update action), I came up with a kind of fix (shame) adding !important to line 52 of global.css in advanced-custom-field-pro/css/global.css
    So turning:

    .acf-visible { display: block; visibility: visible; }
    .acf-hidden { display: none; visibility: visible; }

    in:

    .acf-visible { display: block!important; visibility: visible; }
    .acf-hidden { display: none!important; visibility: visible; }

    prevent inline styles injected by Tabify to overwrite ACF styles.

    There’s still the need to inspect if this could be enough or there’s any other compatibility issue especially concerning data.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Compatibility with ACF 5’ is closed to new replies.