New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bad archive version #1067

Closed
franck-serot opened this Issue May 13, 2013 · 3 comments

Comments

Projects
None yet
2 participants
@franck-serot

franck-serot commented May 13, 2013

Hi,
Except I'm mistaken, the actual archive version of Font Awesome is 3.1.0 on the website.
The version 3.1.1 is expected.
I tried to test the feature "Stacked Icons" with the actual version, but it's not working
Could you please check and update the archive ?
Thank you in advance for your feedback ?
Best regards,
Franck

@davegandy

This comment has been minimized.

Show comment
Hide comment
@davegandy

davegandy May 13, 2013

Member

I don't know what an archive version is. You mean the zip file? How are you determining the version?

Member

davegandy commented May 13, 2013

I don't know what an archive version is. You mean the zip file? How are you determining the version?

@franck-serot

This comment has been minimized.

Show comment
Hide comment
@franck-serot

franck-serot May 13, 2013

I opened archive downloaded from the website http://fortawesome.github.io/Font-Awesome/, then the file font-awesome.zip\font-awesome\css\font-awesome.css.
And I could read this string : Font Awesome 3.1.0
I think the archive is not updated.

franck-serot commented May 13, 2013

I opened archive downloaded from the website http://fortawesome.github.io/Font-Awesome/, then the file font-awesome.zip\font-awesome\css\font-awesome.css.
And I could read this string : Font Awesome 3.1.0
I think the archive is not updated.

@davegandy

This comment has been minimized.

Show comment
Hide comment
@davegandy

davegandy May 13, 2013

Member

It was an oversight on updating that version. However, this causes no problems as that version string only drives caching for the font. Since the font files did not change between 3.1.0 and 3.1.1, this is not a problem.

Member

davegandy commented May 13, 2013

It was an oversight on updating that version. However, this causes no problems as that version string only drives caching for the font. Since the font files did not change between 3.1.0 and 3.1.1, this is not a problem.

@davegandy davegandy closed this May 13, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment