Support

Account

Register Login

Forum Replies Created

  • Ok. I’ve had a look at the actual code and based on that, I’ve opted to unhook the current ACF functions and replaced them with my own. So with slight modification, this is the result:

    
// Integrating Advanced Custom Fields:
remove_filter( 'acf/settings/save_json', 'settings_save_json' );
add_filter( 'acf/settings/save_json', function() {
    return get_stylesheet_directory() . '/Library/Acf-Json';
} );
remove_filter( 'acf/settings/load_json', 'settings_load_json' );
add_filter( 'acf/settings/load_json', function( $paths ) {
    array_push(
        $paths,
        get_stylesheet_directory() . '/Library/Acf-Json',
        get_template_directory() . '/Library/Acf-Json'
    );
    return $paths;
} );

    This seems to be the most effective way of getting ACF settings to use the parent theme as a fallback.

  • Thanks for your help! I’ll need to look into that.

  • Ok, that’s great information, thanks.

    The thing I’d like is, at minimum, to be able to create and define ACF field groups in a parent theme. If there are no database entries for those field groups, then ACF should continue to use the JSON list. Here’s my code for selecting saving sites:

    
// Integrating Advanced Custom Fields:
add_filter( 'acf/settings/save_json', function() {
    return get_stylesheet_directory() . '/Library/Acf-Json';
} );
add_filter( 'acf/settings/load_json', function( $paths ) {
    unset( $paths[0] );
    $paths[] = get_template_directory() . '/Library/Acf-Json';
    $paths[] = get_stylesheet_directory() . '/Library/Acf-Json';
    return $paths;
} );

    Here’s what I’m experiencing:

    1. Activated the child theme
    2. Checked the CPTs, fields are present and accounted for.
    3. For consistency’s sake, activated the parent theme and looked.
    4. CPTs are showing the custom fields just fine.
    5. Switched back to the child theme.
    6. Check the Custom Fields index page. There are NO field groups listed, whatsoever.
    7. Switch back to the parent theme and look.
    8. Custom Fields shows no field groups.

    If you could point me in the direction of the code where all this magic happens, I’d be able to suss out the way it works myself. But I’m confused, because it seems like there must be a field, perhaps in thw wp_options table, that says what editable fields exist? Otherwise, where did the fields go?

    Thanks so much for your assistance!!

Viewing 3 posts - 1 through 3 (of 3 total)