Support » Plugin: Font Awesome » Icon not showing for unlogged users

  • Resolved Smexhy

    (@smexhy)


    Alright, so this is pretty strange one. I use your plugin, because my theme and even some plugins doesn’t support version of FA 5 yet.

    I needed ver 5 because there was icon added regarding Google Pay. I want to show this icon in my footer, however it won’t display to unlogged users for some reason.

    I tried deleting all sorts of caches, local, cloudflare, browser, but it seems that caches aren’t the problem. Do you have any idea what is possibly blocking the icon from loading only for unlogged users (guests)?

    By the way, I can clearly see the icon when looking through elements, it’s just not on the frontend:

    https://cln.sh/v56M7f

    The reason I know this plugin is somehow behind this is, because when I add an older version of the FA (without this plugin) it will show the icon just fine.

    Thanks for any head ups

    • This topic was modified 4 months, 1 week ago by Smexhy.
    • This topic was modified 4 months, 1 week ago by Smexhy.
    • This topic was modified 4 months, 1 week ago by Smexhy.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter Smexhy

    (@smexhy)

    Quick update: it wasn’t exactly caching behind this, but caching plugin as whole, specifically WP Rocket and option “Minify CSS files”

    Excluding FA plugin in WP Rocket options wouldn’t help, so I had to disable that option permanently for now.

    • This reply was modified 4 months, 1 week ago by Smexhy.
    • This reply was modified 4 months, 1 week ago by Smexhy.
    • This reply was modified 4 months, 1 week ago by Smexhy.
    jbravo8212

    (@jbravo8212)

    Solution worked for me! Thanks Smexhy! Drove me nuts all day!

    abelador

    (@abelador)

    Helped me too, ty very much.

    • This reply was modified 4 months ago by abelador.
    Plugin Author mlwilkerson

    (@mlwilkerson)

    One possibility for what’s going on here, depending upon how that “Minify CSS files” feature works, and maybe also whether you’re using this plugin’s conflict detection feature to block conflicting versions of Font Awesome from being loaded by other themes or plugins (a very common scenario on WordPress):

    The minification feature probably works by detecting when stylesheets are being enqueued and then bundling them all together, minifying them in the process, and then enqueuing its own resulting stylesheet instead of the constituent ones. I wonder whether some conflicting Font Awesome CSS from another theme or plugin is being included in that minified bundle. If so, it might cause unexpected results like you’ve described.

    Now suppose you used this plugin’s conflict detection feature to detect and block such a conflict. It would make a difference whether you ran conflict detection while the CSS minifier is enabled or disabled. And then if you changed the minification setting after using conflict detection to block the conflict, you might find that the previously blocked conflict shows up again. So the minifier might be creating something of a moving target for you if you’re trying to use the conflict detector to block a conflict.

    This is all just educated guesswork, based on how this plugin is implemented and inferring how it might interact with a CSS minifier. Your mileage may vary.

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