Support » Plugin: Font Awesome » Plugin won’t activate

  • kikib

    (@kikib)


    I’m using Divi theme from elegant themes. I was able to add “Font Awesome” plugin. However, I was unable to activate the plugin. Every time I click on “Activate”, the page refresh and still show that the “Font Awesome” plugin isn’t activated.

    How do I fix it? All I could think of that maybe it was because I added font awesome pro cdn url in the <head> area that is preventing the plugin from activating.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author mlwilkerson

    (@mlwilkerson)

    Thanks for the report. I have a copy of the Divi theme and I tried it alongside our Font Awesome plugin and could not reproduce the problem you’ve reported. So I wonder if perhaps there’s more going on with your setup that is different from what I have here. For example, are there any add-ons to Divi that you’ve enabled?

    I’d like to be able to investigate this further, if possible, to make sure we don’t have some incompatibility with Divi. I’d need to be able to reproduce the problem, or get more diagnostic info from you.

    In the meantime, I looked at your linked web site and I can see that you have a <link> in your <head> referencing our Pro CDN. It looks like it’s getting a 403 error when trying to load. This is probably because you’ve not yet added test.idsite.com to your Pro CDN domains in your fontawesome.com account. Add any subdomains you intend to use.

    If you do that and it works for you, you don’t need to use our WordPress plugin. But the plugin does make it easier to change versions, change from webfonts to svg and back, and to solve some basic compatibility problems that we often see in the WordPress world when other plugins or a theme attempt to load their own incompatible versions of Font Awesome. So far, it looks like you don’t have any such conflicts on your web site.

    Plugin Author mlwilkerson

    (@mlwilkerson)

    I’ve just released version 4.0.0-rc8. Since it eliminates a class of potential problems with compatibility with other WordPress plugins, it _might_ make a difference in this case. Could you give that new version a try?

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