Add version to font url

  • Resolved Alexander Guskov

    (@forcesail)


    4 months ago

    Hello,
    many thanks for the great plugin. It really improve performance.

    I’d be happy to improve performance even more caching font files on client side adding expiration date through mod_expires.c in .htaccess like:
    ExpiresByType font/woff2 “access 365 day”

    I don’t like to set Cache-Control “must-revalidate” because it significantly drops cache optimization.

    The problem is that if font files change cache would clean up but if url (in <link) had version parameter based, say, on file date the problem would exists.

    Could you add version parameter to <link like:
    <link html=”….woff2?ver=1455555999′

    and to css-file correspondingly, please

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    I’ll look into that, but I think that’s doable! I’ll keep you posted!

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Hi again,

    I’ve implemented your suggestion in this beta. Could you give it a try?

    Let me know if that resolves your issue!

    Thread Starter Alexander Guskov

    (@forcesail)

    Hello Daan,
    Sorry for the delay.

    I have checked out your Beta and figured out that you have put in just a part of the great job:
    1) you have put in version to css-file that is great but it works out just after manual refreshing cache (I’d make up that the new version should reconstruct css-file at update).
    2) you have forgotten about “Load Early” links (it still keep suffering unversioned):
    <link id=’omgf-preload-0′ rel=’preload’ href=’//test.com/wp-content/uploads/omgf/roboto-condensed-font/roboto-condensed-normal-latin-400.woff2‘ as=’font’ type=’font/woff2′ crossorigin />

    One thing more that I didn’t mentioned before: it would be even more great if plugin created woff -file too (cool people still use outdated appliances).

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    it would be even more great if plugin created woff -file too

    You’re the first to ask about this. I’ll make a note and if more people ask about it, I’ll make sure to implement it. WOFF2 has a 97.54% adoption rate in browsers, though. Less than 1 percent under WOFF.

    but it works out just after manual refreshing cache

    Of course, cache needs to be refreshed, and the CSS files need to be rewritten. I thought that made sense, so I figured I didn’t have to explain that. There’s no way to work around this.

    you have forgotten about “Load Early” links

    You’re right! I forgot about those. I fixed it in this beta.

    Thread Starter Alexander Guskov

    (@forcesail)

    Thank you, Daan. Now it works as I would expected with adding version to file-name.

    I would just add regeneration css-file (not the entire set) while updating, otherwise the updated plugin clients know nothing about the great future that you have just added and will suffer on without this future.

    Regarding 2,5% of browser users: it’s a lot. There is just a few or even noone IT-specialists among them, but, say Warren Buffett among them. But it’s very unlikely that he writes a claim to the plugin support blog. He just get out from the site opened on his IE11 on his Windows7 ??

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    I had to Google who that guy was ?? Happy to hear it works now to your liking.

    I’ll consider adding a migration script before I release this in a stable release.

    When you have the time, I would highly appreciate a review!

    You can do so here.

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