Yes this is something I’m open to, and variations of this have been suggested. I do not have an ETA for the next version of this plugin currently.
Thanks for considering it! No timelines expected on a free plugin, just wanted to log the suggestion.
For kits intended for use on only one site, the security issue can be mitigated by restricting to a certain domain. But we have some cases where we want to keep it open so we can let a bunch of domains make use without having to login to fontawesome.com and allow each one individually.
FYI, I ended up spending some time on this tonight along with a few other updates I’ve been sitting on. It’s currently in version 4.0.7 of this plugin. I haven’t fully launched that version yet but it can be downloaded here:
https://wordpress.org/plugins/advanced-custom-fields-font-awesome/advanced/
Go to “ADVANCED OPTIONS” and download the “Development Version” if you are able to test it out.
It isn’t 100% what you asked for (a constant to be defined in wp-config). It uses a WordPress filter to set this value, as well as potentially the kit token for people who want to preconfigure that as well.
From the changelog:
- 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.
