• Resolved miloradt

    (@miloradt)


    I love this plugin and I think it is going to help my users quite a bit. However, I am using a plugin to create custom write fields for all users, and these custom fields show up in every new tab.

    The plugin I am using is Advanced Custom Fields 3.1.7.

    Is there a way for Tabify Edit Screen to recognize custom fields and allow the user to assign them to tabs as well? Or at least to limit the custom fields to only one tab?

    I have not tested Tabify Edit Screen with alternative custom fields plugins like More Fields. I will try this some time this week and let you know if it behaves differently.

    Thanks! Keep up the good work!

    http://wordpress.org/extend/plugins/tabify-edit-screen/

Viewing 9 replies - 31 through 39 (of 39 total)
  • Plugin Author Marko Heijnen

    (@markoheijnen)

    I will look into that later today. I can see the issue since it will automatically set the metaboxes that didn’t got added to the list on the last tab if I remember correctly.

    There is a filter for that. tabify_default_metaboxes or tabify_default_metaboxes__{$post_type}.

    Does ACF toggle any classes on the meta boxes? If so, maybe Tabify can exclude show/hide if the ‘acf-hidden’ class isn’t on the meta box. (or whatever the name is, maybe we can generalize it so any plugins can use it)

    @scott Kingsley Clark

    Yep, I think this would be a good idea. Something like “tabify-ignore”.

    Then all 3rd party plugins which need tabify to ignore the metabox can use that.

    What do you think?

    That’s what I was thinking, something generalized for more compatibility. I think that would be perfect and the easiest for both plugins to live along side each other without compromising functionality or additional dev time.

    @marko Heijnen

    How does this sound to you?

    In the next version of ACF, I’ll add classes of “tabify-ignore” to the metaboxes which need to remain hidden.

    Cool beans

    Plugin Author Marko Heijnen

    (@markoheijnen)

    Yes that is fine too. I still think the filter ‘tabify_default_metaboxes’ would be the best solution but having a javascript seems a good idea.

    Reason why the filter is better is that I don’t add the classes my javascript code tries to manipulate.

    Aah,

    I see! I’ll look into the hook this weekend!
    Doe you have any online docs for the hook?

    Plugin Author Marko Heijnen

    (@markoheijnen)

    Unfortunately not. It is something on my list. I will try to release an update of the plugin tomorrow and then I start to get some docs online.

    I’ve solved the issue.
    I added a class to my metaboxes that use a style of “display:none !important”

    This overrides the js hide / show and makes ACF work perfectly with Tabify.

    These patches will be in the next version (3.5.1)

Viewing 9 replies - 31 through 39 (of 39 total)
  • The topic ‘[Plugin: Tabify Edit Screen] Compatibility with other custom fields plugins’ is closed to new replies.