Hi! Thanks for your reply.
Well yes that is true.
But the purpose why I´m using acf-composer (which in turn is using acf-builder), is to avoid using AdvancedCustomFields like its normally intended.
Feel free to open an issue up on the ACF Composer repo with what you’ve attempted so far and I’ll help you figure it out. I haven’t used ACF extensively for this kinda stuff since Gutenberg, so I’m not entirely sure at a glance.
Also, for “field partials” – if you used my ACF Builder guide at some point with get_field_partial(), it should be available in it’s same form as $this->get() while in one of your ACF Composer field classes (undocumented).
Hi @Log1x!
I managed to get my initial issue to work. Read through your code a couple of times and figured out what I was missing.
Thanks for hinting about get_field_partial() and $this->get(), hadn´t read your guide before. Good stuff! This functionality is exactly what I was looking for.
Curious tho, you said you “haven’t used ACF extensively for this kinda stuff since Gutenberg”. How come? Because that is just what I´m about to do; compose acf-blocks with fields using ACF Composer
Hm, I have a similar dichotomy: Gutenberg blocks (inline) or posts (and these placed as Gutenberg block).
Ideally, one has the choice: Gutenberg blocks that are mapped to posts.
I’ve mainly been working with native blocks as it is still able to give you that “editor experience” compared to swapping between ACF’s preview/edit modes – but it is also incredibly more time consuming making ACF Blocks a rather sane choice, especially with InnerBlock support (which I’ll have to PR into ACF Composer when I have time unless someone would be so kind)