• Chris

    (@pma4life)


    I guess this would be a feature request, but would it be possible to hide the various project names under kits? Or perhaps select by token, etc? Since I am using the same FA account for various clients, but would not want clients able to see other kits other than their own. I suppose the same goes with the API token, if there was a filter where we could add it in code vs in the CMS.

    Thanks for all of your hard work on this fantastic plugin!

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

    (@mattkeys)

    I’ve got an as-yet unreleased version of this plugin with adds some new filters for kits that may unintentionally accomplish your goals.

    The API token + chosen kit ID can be set using a filter in your functions.php or similar.

    If/when they are set in that way, they do not appear in the ACF Font Awesome settings page anymore. Instead there is a line of text reminding people that those settings have been set programmatically using the filter.

    I was looking for testers for some of the new functionality of this release and nobody has stepped up to help test so it’s sorta languished for a while now.

    If you are interested in testing I’d appreciate your feedback. It can be downloaded here:

    https://wordpress.org/plugins/advanced-custom-fields-font-awesome/advanced/

    Go to “ADVANCED OPTIONS” and download the “Development Version”

    • 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.
    Thread Starter Chris

    (@pma4life)

    Hey Matt, thanks for the amazingly quick reply. I will give this development version a whirl. I am currently working on revising my base theme, so this works out. Thanks again!

    Plugin Author Matt Keys

    (@mattkeys)

    Great, looking forward to some feedback from a real life tester 🙂

    Here is the full change log for the development version

    = 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
    Plugin Author Matt Keys

    (@mattkeys)

    Have you been able to do any testing with this new version?

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