WPIntell

Source evidence

Advanced Custom Fields compatability

Tealium · support · 2016-03-15T23:29:00+00:00

mixedsentiment
lowseverity
0.63relevance
1replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

4 / 34 rows with source links

11.8% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

30 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
lelandrb resolved
All Advanced Custom Fields uTag displays are pretty pointless in their current state. Look like so: "book_now_system": [ "field_562c493397c4e" ] All of the ACF-generated fields show this. Pretty big pain since I don’t know of an easy way to de-register the 100+ fields used across the site in one fell swoop. https://wordpress.org/plugins/tealium/ Hi, It looks like ACF is maybe using the standard WordPress meta data concept to just store a reference to the data for each custom field, rather than the actual data. ACF has an export feature, so you might be able to manipulate the output of that into a list of field names in a comma separated list to add to the data layer exclusions option in the Tealium plugin settings. If you run something like this, pasting in the code from an ACF PHP export in a script outside of WordPress that should hopefully do the trick: <?php $names = array(); function register_field_group($groups) { global $names; foreach ($groups['fields'] as &$value) { if (!empty($value['name'])) { $names[] = $value['name']; } } } /* -- PASTE IN OUTPUT FROM ACF PHP EXPORT -- e.g... if(function_exists("register_field_group")) { register_field_group(array ( )); } */ echo implode(', ', $names);

Comments

1 shown
Tealium 2016-07-20T16:39:00+00:00

Hi, It looks like ACF is maybe using the standard WordPress meta data concept to just store a reference to the data for each custom field, rather than the actual data. ACF has an export feature, so you might be able to manipulate the output of that into a list of field names in a comma separated list to add to the data layer exclusions option in the Tealium plugin settings. If you run something like this, pasting in the code from an ACF PHP export in a script outside of WordPress that should hopefully do the trick: <?php $names = array(); function register_field_group($groups) { global $names; foreach ($groups['fields'] as &$value) { if (!empty($value['name'])) { $names[] = $value['name']; } } } /* -- PASTE IN OUTPUT FROM ACF PHP EXPORT -- e.g... if(function_exists("register_field_group")) { register_field_group(array ( )); } */ echo implode(', ', $names);