• Resolved Jules Colle


    Hi, I’m referring to this topic of 2 years ago: https://wordpress.org/support/topic/multisite-support-382/

    We are having the same problem: we have a multisite network with FA pro, where it seems that we need to include the api key in every single website we set up. We will probably write a custom function that adds the key dynamically to each website since we don’t want to do this manually, but just wondering if you have been able to work out something structurally in the meanwhile?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Matt Keys


    Hey @jules-colle,

    Sorry I normally get email notifications when new support requests are made but I didn’t see one for your message here. Just saw it now after helping with another thread.

    There is new functionality in an unreleased beta of this plugin that has what you are looking for. I am looking for testers.

    If you can test it our I would appreciate your feedback. It can be downloaded here:


    Go to “ADVANCED OPTIONS” and download the “Development Version” if you are able to test it out.

    From the change log:

    = 4.0.7 =
    * Added support for FontAwesome "Sharp" family icons
    * Added support for user uploaded duotone icons in kits
    * Updated icon initialization for better compatibility with REST API, and a variety of third party site builder plugins that integrate with ACF fields.
    * Added filter (ACFFA_fa_api_key) to allow for the ability to programmatically set the FontAwesome API key.
    * Added filter (ACFFA_fa_kit_token) to allow for the ability to programmatically set the FontAwesome kit token.
    * Limited role of Select2 'dropdownCssClass' and 'containerCssClass' arguments to avoid conflicts with other plugins using older/non full feature versions of Select2
    • This reply was modified 4 months ago by Matt Keys.
    Thread Starter Jules Colle


    Hi @mattkeys,

    Thanks! And sorry for the late reply. I tested it out and it works great!

    I also like how you display “The API key has been set programatically using the “ACFFA_fa_api_key” filter.” in the settings page. Nice touch!

    I’m just wondering about the naming. Your other filters seem to use lowercase characters, like acffa_kit_version and acffa_kit_license, while the new filters use ACFFA. Will you keep it this way or is it something I should be aware will change in the official release?

    For completeness (and others who might find it helpful) here’s the full code I use to programatically set the settings for my multisite network.

    // Set the ACF-fontawesome plugin settings
    add_filter( 'acffa_kit_version', function($fa_version) {
    	return '6.x';
    } );
    add_filter( 'acffa_kit_license', function($fa_license) {
    	return 'pro';
    } );
    add_filter( 'ACFFA_fa_api_key', function($fa_kit_token) {
    } );
    add_filter( 'ACFFA_fa_kit_token', function($fa_kit_token) {
    	return 'xxxxxxxxxx';
    } );
    Plugin Author Matt Keys


    Thanks for testing @jules-colle! This is a pretty big update to the plugin as it changes how things load themselves in very early on in the process of initialization so I’ve been eager to get it into more hands for more validation.

    Your point about ACFFA vs acffa is a good one and I didn’t notice it. I should stick with the lowercase filters to avoid confusion. It wasn’t intentional, just how my brainwaves have evolved overtime on that one I guess.

    Thread Starter Jules Colle


    Thanks! I’ll add both filter names for now so it doesn’t break when we update the plugin. Looks good to me. We are using it in production now. Looking forward to the official release!

    Plugin Author Matt Keys


    I’ve launched 4.0.7 today.

    I looked into standardizing those filters. It seems almost everywhere else I made uppercase ACFFA_ the norm. The “lowercased filters” you found are sort of undocumented functionality already out in the wild. I thought about changing them to be uppercase, but I’ve decided against it as I don’t want to mess up anyones code referencing the lowercase version.

    So it will just be a little quirk in the code. I’ll try and stick to uppercase going forward.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.