GD Plugin Conflict with Avada Theme

This topic contains 10 replies, has 4 voices, and was last updated by  Marc Fritz 6 years, 4 months ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
  • Author
    Posts
  • November 19, 2018 at 2:38 pm #455018

    Marc Fritz
    Free User
    Post count: 28

    Hi,

    After updating to the latest version of the GD-plugin, the icons throughout all of the pages of my website are not displaying correctly anymore (https://www.leisurecard.com/)
    The issue seems that the plugin is adding an inline SVG and replacing Avada’s font. Please see the screenshot linked below for details.

    I reached out to the support team of the theme, but they’re telling me that it’s caused by the GC plugin and that I should reach out to you guys.

    Thanks,

    Marc

    November 19, 2018 at 2:45 pm #455023

    Alex Rollin
    Moderator
    Post count: 27815

    Hello,

    Yes, GD has been updated to use FA V5 JS (SVG). We recommend that you share this link with the theme author https://wpgeodirectory.com/the-font-awesome-v5-wordpress-problem/

    Please share WP Admin and Login URL in a private reply and we will check to see if there is a workaround.

    November 19, 2018 at 2:49 pm #455024

    Marc Fritz
    Free User
    Post count: 28
    This reply has been marked as private.
    November 19, 2018 at 4:16 pm #455043

    Alex Rollin
    Moderator
    Post count: 27815

    I have flagged your topic for the developers. Thanks for your patience while we look into it.

    November 23, 2018 at 10:54 am #455583

    José Díaz Blanco
    Buyer
    Post count: 21
    This reply has been marked as private.
    November 23, 2018 at 4:30 pm #455650

    Alex Rollin
    Moderator
    Post count: 27815

    Hi Jose,

    thanks for writing in about the issue. We are working on a solution. You can stay tuned here or make your own topic if you have something else to report.

    November 27, 2018 at 3:44 am #456026

    Marc Fritz
    Free User
    Post count: 28

    Hi Alex,

    Could you please provide me with an update?

    Did the developers get a chance to look into the issue yet?

    I updated to the newest GD version, but the icons on my website are still not displaying correctly.

    Thanks,

    Marc

    November 27, 2018 at 1:09 pm #456071

    Stiofan O’Connor
    Site Admin
    Post count: 22956

    As explained in the blog post posted above the issue is not ours to fix, it s WP + Font Awesome thing, if any plugin/theme you have active is using FA5 JS then you will have the same issue, the only real solution is to also use FA5 JS which we do and AVADA will eventually have to do no matter how much they resist.

    Stiofan

    December 1, 2018 at 3:13 am #456628

    Marc Fritz
    Free User
    Post count: 28

    Hi Stiofan,

    Thank you for your reply! Based on Alex’s reply I thought that your developers were checking into the issue.
    I passed on your comments and the above provided link to the Avada support team.
    Here’s their reply:

    “I believe it is quite a difficult task for us to change our FA setup immediately.

    There are a few points that we would like to mention here

    1) The KB item shared by plugin support has the following mentioned -> http://prntscr.com/lnxstf. If they check source after disabling the plugin and its add-ons, we are using standard approach. Here is a screenshot for reference -> http://prntscr.com/lnxu3k, but the source is still being modified here.

    2) Plugin author also provides another plugin to fix this issue -> https://github.com/AyeCode/fix-font-awesome. So maybe they can help you implement this

    3) Additionally, I see they themselves claim compatibility with Avada -> http://prntscr.com/lnxuxr. So it should not be hard for them to add a check for Avada in their code.

    4) On top of that, we enqueue our file with “font-awesome” handle -> http://prntscr.com/lnxx5e. While they do with “fontawesome-css” handle. This is with respect to the response here, https://prnt.sc/lny38n.”

    I would greatly appreciate any help to resolve the issue!

    Thanks,

    Marc

    December 1, 2018 at 2:08 pm #456684

    Stiofan O’Connor
    Site Admin
    Post count: 22956

    Hi Marc,

    Not a very encouraging reply :/

    1. FAv5 JS is modifying the source, thats how it works, its not GD doing it.
    2. That plugin simply removes the CSS ver of FA, it won’t fix things that are styled specifically for the CSS ver.
    3. Even if we switch to using the CSS ver with avada the issue will still be exactly the same if any other plugin uses FAv5.
    4. Hmm, not we don’t, we use “font-awesome” i’m not even sure where they got that from, but it just goes to show that other plugins load FA also and that if they load the JS ver then the exact same issue will happen. (Also they are actually using “fontawesome” not “font-awesome” like they claim, their own image shows this)

    I’ll be releasing Claim manager v2 on Monday and then i’ll see what extra efforts i can put into resolving this. At this stage my thinking is to just add an option in GD to use js or css ver and then we can’t be blamed for incompatibilities (we have had support requests for not using the JS ver and now for using the JS ver)…

    Thanks,

    Stiofan

    December 1, 2018 at 11:50 pm #456742

    Marc Fritz
    Free User
    Post count: 28

    Hi Stiofan,

    Thank you, I appreciate you taking the time to write the detailed reply above!

    Yes, I am disappointed in the customer support from Avada.
    It would be awesome if you could take a look at the issue after your release on Monday. I appreciate your help!

    Best regards,

    Marc

  • Author
    Posts
Viewing 11 posts - 1 through 11 (of 11 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
20% Discount Offer
Hurry! Get your 20% discount before it expires. Get 20% Discount