• Resolved lelandrb

    (@lelandrb)


    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/

Viewing 1 replies (of 1 total)
  • Plugin Author Tealium

    (@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);
Viewing 1 replies (of 1 total)

The topic ‘Advanced Custom Fields compatability’ is closed to new replies.