John Huebner

So, I tracked down the problem. I have another plugin has an action on acf/init. This action is used to check for the existence of other types of fields and if they don’t exist then parts of the plugin are disabled.

I believe it’s running on this hook because, well it does not run if acf is not installed. The parts of the plugin that are disabled are disabled by default and only enabled if the field types are found. Changing the other plugin to init instead of acf/init does correct the problem.

I’m guessing that this has something to do with the order that the ‘init’ actions are fired. If your init was before acf’s init then more than likely the problems would not exist.

I’m going to change the other plugin, because I can and then check for the existence of the acf function instead of depending on acf’s hook.

My problem is resolved for now. I’m sure that I only did it this way because I found other plugins doing it this way, so other people may run into the same thing if they also use this plugin.

I would suggest that you either set a priority less than ACF’s (which is 5) or change the hook to your filter to acf/init. I tried both of these options and they both worked, but I’m not sure if there’s anything in the library that you’re using that would cause other issues by doing this.

In your main plugin file you need to change this

add_action( 'init', 'register_fields_font_awesome' );

to this

add_action('acf/include_field_types', 'register_fields_font_awesome');
add_action('acf/register_fields', 'register_fields_font_awesome');