Difficulties updating existing custom font sets

[ar...@updatecontent.com]

I have had difficulties adding a new icon to an existing custom font set.

1. I import the new icon.
2. I generate the font set again.
3. The new icon font displays locally in the demo.html file.
4. I update the four files included in the /font folder as well as the new class in the style sheet of the site I am building.
5. I receive a missing icon for JUST the new icon.
6. I go crazy.

Let me know if I am missing a step somewhere.

Thanks!

[Keyamoon]

That sounds like a caching problem. Try replacing your own @font-face rule with the newly generated one. Alternatively, you could manually change the "cache buster" string at the end of the URLs. Doing so would prevent the browser from loading a cached version of the font.

[jlbre...@gmail.com]

HI, I'm having the same issue. Since we are using Bourbon's @font-face, I haven't figured out a way to cache-bust this yet?

@Keyamoon:
I am confused as to what this means: "Try replacing your own @font-face rule with the newly generated one" (which newly generated one? from where?

Typing this, I've come across my answer: I'll just rename my font with "_v2" or "rev2" or something; that should bust the cache! (Why didn't I think of that before?)

[Keyamoon]

By "newly generated one" I meant the font you generate with the IcoMoon app. Each time you make a change to your font, the @font-face rule that the IcoMoon app generates would add a different cache buster at the end of font URLs. This is basically the same as renaming the font.

[jlbre...@gmail.com]

Just wanted to post back and confirm that my (simple) solution worked. (I now see that I could have also appended each URL string in my font-face call witha cache-busting query-string ('myfont.ttf?=v2') I opted for the rename, because I change it once,and Bourbon does the rest.

Cheers