Reply To: Local JSON fallback?

• tbelknap

• March 4, 2019 at 5:46 am

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!!