Unsupported fields displaying on frontend

  • Afterword

    (@ahateleybrowne)


    5 years, 7 months ago

    I use Advanced Custom Fields on my events to associate them with particular posts (using relationship field types) in the sidebar. With the recent ACF-compatible update it is now getting pulled into the content section. I really like the idea of integrating with ACF, but I don’t want this in my content section as my fields are only peripheral to the event. I tried turning off the feature in the settings but it didn’t remove the “Field type not supported”. I can probably clean it up myself, but it’ll feel a bit hacky. Is this something that will be fixed/adjusted?

Viewing 1 replies (of 1 total)
  • Plugin Author Guido

    (@guido07111975)

    Hi Andrew,

    Because there are many ACF field types and I wanted to avoid compability issues, so I have added this notification. You should be able to hide whole ACF section (including that notification) via the settingspage, but not for a single event. For that you should use Custom CSS, the same applies for the regular event fields by the way.
    I don’t fully understand what you want.. you don’t want those fields in the content section, so they should not be visible in the frontend?

    Guido

Viewing 1 replies (of 1 total)
  • The topic ‘Unsupported fields displaying on frontend’ is closed to new replies.

Tags