Hi James
That’s very kind of you! 🙂
It’s here:
https://dl.dropboxusercontent.com/u/4676147/acf-export-2016-10-25.json
There’s more field groups than just the ones in question; I’m just to trying and avoid missing fields from clones.
– The button field is in ‘Base: Button’
– The flexible layouts are in ‘Hero: Elements’ and is assigned to a ‘Hero’ CPT (but you can reassign this to a page)
– Inside the flex layouts, you’ll find the buttons layout, which is a repeater
– I also included ‘Theme Options: Promo Bar’ – this has a button field too, but isn’t inside a repeater/flex
Any questions, let me know. What I’m trying to do might well not possible – I’m prepared for that eventuality 🙂
Appreciate it,
Hi James
Thank you for the reply!
I think I’m “OK” with the clone field side of things, actually. I was mentioning for context, but I think you’re completely right – it’s irrelevant in this context.
One crucial thing I somehow didn’t mention is that the value I’m trying to get is inside a flexible content layout, nested inside a repeater.
The fields look like:
- Repeater (columns) - attached to a CPT single
- Flex layout blocks (inside columns)
- Text field (inside Flex layout)
- Highlight field (inside Flex layout)
For this reason, get_field('highlight_color', $post_id)
can’t retrieve the correct value.
Through the acf/format_value/type=text
filter, I am able to get the info as per my initial post, including the parent ID and the parent_layout key.
So in this case, the current field ID is 2126
and it’s parent is 2123
.
What I’m therefore trying to do (in pseudo code) is:
Get the value of a field who's parent is 2123 and name is highlight_color
Thanks again
Hey @solverat – just a ‘quickie’ on the Yoast snippet – we had a couple of issues getting it to work (because of Yoast’s documentation, it seems!)
Details in this link: https://github.com/Yoast/YoastSEO.js/issues/181
But now that’s done it works like a charm.
Hope it helps 🙂
Hey @solverat
Great news. Thanks for this.
I’ll need a bit of time to just look around and find the boundaries of the plugin and where it is now, and then I can get in touch with you to discuss what you need help with (if anything), but otherwise will try and get it functional in a non-Themosis environment 🙂
The Yoast/ACF plugin looks great too; it’s something we have had a problem with in the past with V2.x of Yoast, and had to append all meta to the_content so the analysis would displaying *something* – it wasn’t pretty or perfect, so this is great too – thanks for sharing.
@solverat Re: Themosis – super awesome; glad you’re finding some success with it. We’re using the Roots.io stack, which is a great way to build the “more conventional” WordPress themes IMO, but we plan on testing Themosis soon as it looks so nice, and very similar to Laravel.
Re: Page Designer – I would agree with @Markus… (of course I would say that 🙂 ) but perhaps with more contributors, it would be easier to keep on top of the ACF core updates as well as integrate some nice things.
Re: Shortcake – great stuff 🙂
@solverat Very nice; we’re looking to build something exactly like that to make it user-friendly for our clients.
Are you using shortcake as well to render elements (like the button)?
Yes same issue on 5.0.8
If I revert back to 5.0.7, they reappear.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Cookie Policy. If you continue to use this site, you consent to our use of cookies.