• I’m super excited about the ability to use custom metadata in my block based layouts. My use case is to generate “listen” buttons for a music release, linking through to places like Bandcamp, Spotify, etc. The custom field data would be a string/URL.

    When I checked in on block bindings in 6.5, my understanding was that you need to use PHP to register your custom field, expose in REST api, and make available for binding. And in the editor, you need to edit markup directly to add the binding (i.e. it’s not in the UI yet).

    I see in 6.6 there are improvements, and you can now automatically save/persist changes from the editor. Cool!

    What I want to know is – to use block bindings, do I still need to set it up in PHP (e.g. a plugin/snippet)? Or is it possible to use block bindings “code free” in 6.6?

    Feel free to link me to GitHub to follow progress on this powerful feature ??

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator bcworkz

    (@bcworkz)

    I could be wrong, but AFAICT you still need PHP to set up your custom field. What the 6.6 improvements do is cause custom fields to behave in a more intuitive, user friendly manner. It’s more of a UI improvement than a change in the API itself. You cannot add a custom field directly from the editor without setting things up behind the scene.

    Github summary of block bindings API discussions.

    Thread Starter Rua Haszard

    (@haszari)

    Thanks for the pointers @bcworkz , I’ll explore in GitHub, I’m keen to find out when/how to use custom fields/custom meta without PHP.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.