Bypassing data storage in core meta tables

By default, the plugin does not bypass storage of metadata to the core meta tables as doing so can create issue with other plugins that are dependent on meta data existing in the core meta tables.

However, you may configure your site to bypass core tables where data is stored in a custom database table. This is broken down into two parts:

1. Bypassing field values
2. Bypassing field key references (used internally by ACF to map field names to field keys)

Important considerations before choosing this option

If you decide to bypass data storage in core meta tables, it is important you bear the following in mind:

1. You must be using ACF JSON if you decide to bypass the field key references as well as the field values. If you disable key reference storage, ACF won't be able to retrieve field values from any source.
2. Many third party plugins expect — and even depend — on data in the core meta tables. Be sure you don't need to use these plugins or be prepared to implement some form of workaround should the need arise.
3. Without meta data in the core meta tables, WordPress meta queries will no longer function. If you want to use custom table data in conjunction with WP_Query, see this article.

How to bypass field values

To bypass storage of meta values where a custom table is found, use the following filter:

 * Disables storing of meta data values in core meta tables where a custom 
 * database table has been defined for fields. Any fields that aren't mapped
 * to a custom database table will still be stored in the core meta tables. 
 */
add_filter( 'acfcdt/settings/store_acf_values_in_core_meta', '__return_false' );

How to bypass field key references

To bypass storage of ACF field key references for fields mapped to a custom database table, use the following filter:

Note: you should only do this if you are using ACF JSON. If your field groups aren’t represented in JSON files, you will have problems storing and retrieving data.

 * Disables storing of ACF field key references in core meta tables where a custom 
 * database table has been defined for fields. Any fields that aren't mapped to a 
 * custom database table will still have their key references stored in the core 
 * meta tables. 
 */
add_filter( 'acfcdt/settings/store_acf_keys_in_core_meta', '__return_false' );