WordPress.org

Support

Support » Plugins and Hacks » Genericon'd » [Resolved] Slim Jetpack Conflict

[Resolved] Slim Jetpack Conflict

Viewing 5 replies - 1 through 5 (of 5 total)
  • The conflict was that Jetpack didn’t include the whole of Genericons, and since we (oddly correctly) are using the same call for the CSS, theirs just happens to take precedence.

    Anyway. Fix? They need to include the whole Genericons CSS. Nothing I can do about it :/

    Thanks, makes perfect sense

    Okay, in the interests of all things, I’ve made a change to Genericon’d to essentially force Jetpack and the like to shut up and use my fonts, thanks. It’s … ugly, and I don’t like it, but until Jetpack and it’s brethern learn to share and load things in a friendly way (that is – not load Genericons unless the mobile theme is in use), every time I update the font set, the conflict would come back.

    *sigh*

    Sorry that it’s such a bother, but I appreciate your efforts to bear with their “weaknesses”, lol!

    It’s not necessarily their weakness 😉 The situation is complicated because I would have to ensure I always load first, taking priority, but what if I’m the one who’s delayed on an upgrade? Yick.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[Resolved] Slim Jetpack Conflict’ is closed to new replies.
Skip to toolbar