Title: Multisite support
Last modified: April 4, 2022

---

# Multisite support

 *  [Dountill](https://wordpress.org/support/users/dountill/)
 * (@dountill)
 * [4 years, 2 months ago](https://wordpress.org/support/topic/multisite-support-382/)
 * After a recent update most of the working subsites in my multisite are having
   missing items. Also, new created subsites are automaticly set to FA version 6.0
 * I have an API code, but can’t seem to find a place where I can set it for my 
   whole multisite network. Is that correct or am I missing something? If not, will
   there be support for multisites?

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Author [Matt Keys](https://wordpress.org/support/users/mattkeys/)
 * (@mattkeys)
 * [4 years, 2 months ago](https://wordpress.org/support/topic/multisite-support-382/#post-15526432)
 * Hey [@dountill](https://wordpress.org/support/users/dountill/),
 * > After a recent update most of the working subsites in my multisite are having
   > missing items.
 * Can you elaborate on what you mean by missing items?
 * > Also, new created subsites are automatically set to FA version 6.0
 * That is true that the default behavior of this plugin is to use the latest version
   of FontAwesome unless a previous version was already in place (from an upgrade
   of the plugin) or a previous version is manually selected.
 * There is a filter you can use to override the major version number that I believe
   should apply across all of your subsites: **ACFFA_override_major_version**, you
   can return a value of 4, 5, or 6 to this filter.
 * > I have an API code, but can’t seem to find a place where I can set it for my
   > whole multisite network. Is that correct or am I missing something? If not,
   > will there be support for multisites?
 * I think you are speaking of a FontAwesome API Token. This only applies to version
   6.x of FontAwesome in this plugin. It sounds like in multisite you are having
   to set this token individually for each of your sites? This isn’t something I
   had considered during development but I could see how that might be a pain. I’d
   have to research what the best way to approach “global” settings for this would
   be. In addition to the API Token there are other settings that would probably
   need to be considered.
 *  Thread Starter [Dountill](https://wordpress.org/support/users/dountill/)
 * (@dountill)
 * [4 years, 2 months ago](https://wordpress.org/support/topic/multisite-support-382/#post-15528123)
 * Thanks for your reply. Some of the icons are missing in the list, that was what
   I ment with missing items. I tried to use the filter, although it does seem to
   work, all the selectors are still showing the new v6 method of selecting/searching
   for icons.
 * Since this plug-in updated I opted in for FA Pro as an attempt to fix the above
   issues and upgrade to a newer version. Since I have a few multisites with over
   100 subsites in them it is indeed a lot of work to put a API code in them.
 * Also, I don’t want my users to see my API code. I’ll surely keep an eye out for
   updates on your plug-in. But for now I think in my situation it is better to 
   role back to the automatic v5 version.
 *  Plugin Author [Matt Keys](https://wordpress.org/support/users/mattkeys/)
 * (@mattkeys)
 * [4 years, 2 months ago](https://wordpress.org/support/topic/multisite-support-382/#post-15529283)
 * > Some of the icons are missing in the list, that was what I ment with missing
   > items.
 * Thanks, I got another report from another user that the icon manifest for 5.x
   free icons is incorrect. I’ve fixed it on my end now but unfortunately it is 
   still cached through the CDN and I am waiting to hear back from them on how to
   clear that cache.
 * In the meantime it does not affect the 5.x pro manifest.
 *  Plugin Author [Matt Keys](https://wordpress.org/support/users/mattkeys/)
 * (@mattkeys)
 * [4 years, 2 months ago](https://wordpress.org/support/topic/multisite-support-382/#post-15530478)
 * The issue with missing icons in FontAwesome 5.x free should be resolved with 
   todays release of v4.0.3 of this plugin. Let me know if you continue to see any
   issues there.
 * As for the multisite improvements I think they are good suggestions. I’ll need
   some more time in my schedule to setup a multisite dev/testing environment, but
   they are on my list.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Multisite support’ 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/)

 * 4 replies
 * 2 participants
 * Last reply from: [Matt Keys](https://wordpress.org/support/users/mattkeys/)
 * Last activity: [4 years, 2 months ago](https://wordpress.org/support/topic/multisite-support-382/#post-15530478)
 * Status: not resolved