Title: Error Field type does not exist Last modified: February 2, 2017 --- # Error Field type does not exist * Resolved [John Huebner](https://wordpress.org/support/users/hube2/) * (@hube2) * [9 years, 6 months ago](https://wordpress.org/support/topic/error-field-type-does-not-exist/) * Latest version of ACF 5 Pro, Getting message that field type does not exist Viewing 10 replies - 1 through 10 (of 10 total) * Thread Starter [John Huebner](https://wordpress.org/support/users/hube2/) * (@hube2) * [9 years, 6 months ago](https://wordpress.org/support/topic/error-field-type-does-not-exist/#post-8729415) * 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'); ``` * Plugin Author [Matt Keys](https://wordpress.org/support/users/mattkeys/) * (@mattkeys) * [9 years, 6 months ago](https://wordpress.org/support/topic/error-field-type-does-not-exist/#post-8730464) * I used to initiate the plugin on those hooks as recently as 1.7 * [https://plugins.svn.wordpress.org/advanced-custom-fields-font-awesome/tags/1.7/](https://plugins.svn.wordpress.org/advanced-custom-fields-font-awesome/tags/1.7/) * There were incompatibilities with my plugin alongside the Better Font Awesome plugin (whose library is used in this plugin) that precipitated the switch to using init. * Does 1.7 fix your problems? * Thread Starter [John Huebner](https://wordpress.org/support/users/hube2/) * (@hube2) * [9 years, 6 months ago](https://wordpress.org/support/topic/error-field-type-does-not-exist/#post-8730736) * I think I might be looking at a conflict with another plugin. I’m digging into it now and will get back to you * Thread Starter [John Huebner](https://wordpress.org/support/users/hube2/) * (@hube2) * [9 years, 6 months ago](https://wordpress.org/support/topic/error-field-type-does-not-exist/#post-8730891) * 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. * Plugin Author [Matt Keys](https://wordpress.org/support/users/mattkeys/) * (@mattkeys) * [9 years, 6 months ago](https://wordpress.org/support/topic/error-field-type-does-not-exist/#post-8731427) * Thank you for the thorough debug John. * [adejones](https://wordpress.org/support/users/adejones/) * (@adejones) * [9 years, 5 months ago](https://wordpress.org/support/topic/error-field-type-does-not-exist/#post-8857179) * I am using ACF Pro v5.5.9 with ACF font awesome v1.7.3 and I have the same issue, Font awesome is not appearing in the list of available field types. * Any help appreciated. Thanks. * Thread Starter [John Huebner](https://wordpress.org/support/users/hube2/) * (@hube2) * [9 years, 5 months ago](https://wordpress.org/support/topic/error-field-type-does-not-exist/#post-8857202) * Out of curiosity, what other ACF addons are you using? * [adejones](https://wordpress.org/support/users/adejones/) * (@adejones) * [9 years, 5 months ago](https://wordpress.org/support/topic/error-field-type-does-not-exist/#post-8857297) * Only other add-on i’m using is by some guy called Job Huebner, ACF User Role Field Setting 🙂 * Edit: Disabling that does bring the field type back. - This reply was modified 9 years, 5 months ago by [adejones](https://wordpress.org/support/users/adejones/). Reason: further detail * Thread Starter [John Huebner](https://wordpress.org/support/users/hube2/) * (@hube2) * [9 years, 5 months ago](https://wordpress.org/support/topic/error-field-type-does-not-exist/#post-8857645) * I’ve made an alteration in my plugin to deal with ACF add ons that initialize their fields on non-standard hooks. * [adejones](https://wordpress.org/support/users/adejones/) * (@adejones) * [9 years, 5 months ago](https://wordpress.org/support/topic/error-field-type-does-not-exist/#post-8857683) * Works a treat, many thanks to you. Viewing 10 replies - 1 through 10 (of 10 total) The topic ‘Error Field type does not exist’ is closed to new replies. * ![](https://ps.w.org/advanced-custom-fields-font-awesome/assets/icon-256x256. jpg?rev=3435775) * [Advanced Custom Fields: Font Awesome Field](https://wordpress.org/plugins/advanced-custom-fields-font-awesome/) * [Support Threads](https://wordpress.org/support/plugin/advanced-custom-fields-font-awesome/) * [Active Topics](https://wordpress.org/support/plugin/advanced-custom-fields-font-awesome/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/advanced-custom-fields-font-awesome/unresolved/) * [Reviews](https://wordpress.org/support/plugin/advanced-custom-fields-font-awesome/reviews/) * 10 replies * 3 participants * Last reply from: [adejones](https://wordpress.org/support/users/adejones/) * Last activity: [9 years, 5 months ago](https://wordpress.org/support/topic/error-field-type-does-not-exist/#post-8857683) * Status: resolved