Fontawesome and pagelines


6 posts in this topic

Posted · Report post

Guys,

 

Something keeps happening to fontawesome display in pagelines. This boils down to cross-domain access, caught by Firefox.

 

What I see on one out of three sites is that for some reason fontawesome icons are transferred in https vs http.

I'm running in network mode and have an ssl certificate for one domain only so transfer of the font fails.

 

There are workardounds pointing to .htaccess modifications though your ISP needs header_c complied in Apache for that to work.

 

Thing is: even docs.pagelines.com presents these errors: check out a screenshot at http://www.hajobakker.com/?attachment_id=864

 

 

Setup: wp 3.6.1, network / domain mapping / multilanguage / wp super cache / widget logic

Share this post


Link to post
Share on other sites

Posted · Report post

Hi,

 

This has been brought to our attention before. See here for more info - http://wpvkp.com/font-awesome-doesnt-display-in-firefox-maxcdn/

 

Thanks Danny,

 

For some this is woule be a nice workaround - provided your ISP compiles Apache with mod_headers.c - but not a solution.

Instead of using the original URL, somehow somewhere a variable is overwritten and httpd used for transfer instead of http.

Firefox is not in any way responsible for this behaviour and is basically the only browser adhering to cross-domain standards.

 

If this is the way it is I'll just drop fontawesome and themes making use of it, a shame to think about this but the way it is.

 

Thanks anyway, guess it's time for me to reconsider.

Share this post


Link to post
Share on other sites

Posted · Report post

I understand that the issue does not lie with FireFox or IE and they're following the Cors standard. However, I am not entirely sure why you keep mentioning your ISP, what does your ISP have to do with CORs? I assume you mean your web host provider and not your Internet Service provider ? I will report this to our developers and see if there is anything we can do. However, you will most likely need to use the .htaccess trick provided on the link above.

Share this post


Link to post
Share on other sites

Posted · Report post

Sorry Danny, you're right and I'm tired I guess. I indeed did intend my hosting provider, sorry.

Share this post


Link to post
Share on other sites

Posted · Report post

:D No problem, was just confused thats all. I've created an issue in our tracker, hopefully our devs will be able to provide an alternative. If thats not the case, then you will need to use the .htaccess snippet.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now