• kdsign

• in reply to: How to use WP Term Meta, the easy way!
• December 2, 2016 at 5:10 am

@elliot Now that the update has been released and we know that the fields are copied over the wp_termmeta table, can we delete them from the wp_options table ?

• kdsign

• in reply to: How to use WP Term Meta, the easy way!
• October 23, 2016 at 1:27 am

Great News Elliot!!! Thanks so much! Would it allow to update old values so to clean the options table safely?

• kdsign

• in reply to: Tabify support [ACF 5.0.2]
• July 31, 2014 at 8:09 pm

Since the error seems being not blocking (post save or update action), I came up with a kind of fix (shame) adding !important to line 52 of global.css in advanced-custom-field-pro/css/global.css
So turning:

.acf-visible { display: block; visibility: visible; }
.acf-hidden { display: none; visibility: visible; }

in:

.acf-visible { display: block!important; visibility: visible; }
.acf-hidden { display: none!important; visibility: visible; }

prevent inline styles injected by Tabify to overwrite ACF styles.

There’s still the need to inspect if this could be enough or there’s any other compatibility issue especially concerning data.

• kdsign

• in reply to: Tabify support [ACF 5.0.2]
• July 30, 2014 at 11:58 pm

wow, six days still no ideas ?

• kdsign

• in reply to: Check if layout is used
• July 22, 2014 at 1:57 am

You could register your script in functions.php and then enqueue it right where you need. So, just as a mere example:
in functions.php

wp_register_script( 'gmaps','https://maps.googleapis.com/maps/api/js?v=3.exp&sensor=false', array(), '1.0', true );

and then in your layout code:

elseif( get_row_layout() == 'map' ):

        $google_maps = get_sub_field('google_maps');
        if( !empty($google_maps) ):
        wp_enqueue_script('gmaps');

This will load google’s .js in footer just when you need it.

• kdsign

• in reply to: Can't use conditional fields after last update.
• July 21, 2014 at 11:19 pm

Here too.