• Resolved tatof

    (@tatof)


    I included fontawesome myself on the back & frontend but it doesnt work. I dont want to use the font awesome kit.

    This is what I did:
    1. Change in the options version to 6.x
    2. No token or kit selection.
    3. Tried the acf field (its empty) ??

    Is there a way to fix this? Can’t to use the kit/cdn on this project. No external sources allowed for this project. So no API, KIT or CDN.

    As you can see in this image the icon works but the search doesnt:
    https://devtof.nl/fontawesome.png

    Edit:
    Not using any filters. Working like this worked for the 5.x versions.
    Just want to include my own FA and use a ACF field so the client can choose an icon.

    • This topic was modified 2 years, 8 months ago by tatof.
Viewing 2 replies - 16 through 17 (of 17 total)
  • I am having a similar issue where I need to load FA locally now. I had an API key in the plugin but removed it. I’ve cleared the cache and Enqueue FontAwesome is set to no on the ACF fields. It still enqueues the kit though. Is there something else I need to do to clear it out?

    Thread Starter tatof

    (@tatof)

    Hey Lisa, I found out with the support of the plugin maker that without the api for the backend you can’t use the “smart” search.

    It works fine but you have to type exactly the value your searching for. For example:

    fa-bars works
    menu bars doesnt work

    What I do now and I think is a good solution is include the kit from font awesome with the api and only use it on the backend of all my websites (600+). That way you don’t use to much data but the search works ??

    And in the frontend don’t load fontawesome trough the api. (its an checkbox in the acf field) just load the FA yourself in the frontend ??

Viewing 2 replies - 16 through 17 (of 17 total)
  • The topic ‘Using the plugin without the Kit’ is closed to new replies.