Support

January 14, 2025 at 10:26 am

Hi,

Apologies! I thought I’d replied to this!

The answer is yes and no (That’s a great answer that, Tony! 🙂 ).

ACF is ‘just’ storing custom fields with a post type, so technically EE can already pull in those values using the [EVENT_META_*{meta_key}] shortcode where you pass the key of the custom field to that shortcode in place of {meta_key}. With a ‘standard’ custom field that’s relatively simple, like this:

https://monosnap.com/file/Fujbw8EHs8YhqcxdlQqCodUgBBxhRG

And the shortcode would just be:

[EVENT_META_*default_source]

The output in that specific case would be ‘Testing’.

The ‘problem’ is that ACF also does a bunch of other processing and allows for wayyyyy more custom field types than WordPress does and that’s where you’ll run into problems becuase EE doesn’t know anything about ACF i itself, so the value you get back from ACF may not be the value you expect (it may store the ID of some value from a custom table within the custom field and then have say a Date stored with that ID) ACF knows how to pull the correct data, EE will not.

So yes, as it stands EE will indeed pull ‘a’ value for an ACF field is you pass it the correct custom field meta_key for it… but if that’ll be the correct field is another story.

To pull the correct field another shortcode needs to be created that will pull in the value in the way that ACF wants it to be done, if that’s a hard requirement for you its something we may be able to do with 1/2 support tokens (will need to asses how long it will take before moving forward).