I'm afraid I wasn't paying any attention to see if it was this update that did this or if there are other issues, but we are not getting the Jomsocial Fonts rendered correctly and I noticed this after updating to 3.2.1.3 and checking out the site.

Instead of the normal Jomsocial icons for Exit/Logout, Login, etc., we are getting non-rendered fonts. We are using the default template without any changes and no overrides in CSS in our Site template.

The CSS correctly refers to the /font directory and the jomsocial.eot, woff., etc files.

.joms-icon-lock:before { content: "" }

But it displays exactly like that  or in some browsers just a little box icon.

Timestamp: 8/14/14, 12:29:33 PM
Error: downloadable font: rejected by sanitizer (font-family: "jomsocial" style:normal weight:normal stretch:normal src index:2)
source: oursite.com/components/com_community/tem...t/font/jomsocial.ttf
Source File: oursite.com/components/com_community/tem...t/css/style.dark.css
Line: 0
Source Code:
@font-face { font-family: "jomsocial"; font-style: normal; font-weight: normal; src: url("../font/jomsocial.eot?#iefix") format("embedded-opentype"), url("../font/jomsocial.woff") format("woff"), url("../font/jomsocial.ttf") format("truetype"), url("../font/jomsocial.svg#jomsocial") format("svg"); unicode-range: U+0000-FFFF; }

Hi Kevin,

Can you provide me the FTP access, please? hard for us inspect the issue without FTP.

thank you

We do not allow FTP on production hosts, but I have extplorer available.

I also have our old test system that shows the fonts were working... you can view it at js32.stratacorps.com/index.php?option=co...frontpage&Itemid=815

Hi Kevin,

Did you install the CSS comporessor or enable prevent loading font setting? Please you disabled them if you have any.

This issue caused by your joomla template, please you try use atomic / beez template for testing it, should work fine then.

For more information I suggest you contact your joomla template developer (RocketTheme)

thank you

No, I have not enabled any CSS compressor and am not sure what you mean by "prevent loading font setting" ??

This happened after we updated Jomsocial. I have an archived version of the site using the same exact template at the js32.stratacorps.com URL that I provided and it is working correctly.

Again, both the test archive site before the jomsocial update and the production site (which does not use cache or compression of any kind) are using the same template.

????

Hi Kevin,

are you using IIS right? or nginX ? please you try this solution stackoverflow.com/questions/15521130/goo...-with-mime-type-appl

thank you

No, both servers (js32 testing site and the production actnowracing.com site) are using Apache, standard cPanel hosting installation, both using the same exact server configuration (PHP, MySQL, etc.).

Hi Kevin,

Ehm, weird this issue usually caused by "charset=utf-8" but this is different, may I know your FTP access, please? I will check the code directly.

thank you

I have extplorer installed for file access...we don't have FTP for production projects. Will that work?

Hi Kevin,

I know why this issue happens, because your server cant open this file actnowracing.com/components/com_communit.../font/jomsocial.woff and always redirect to community home page, BUT if you open this js32.stratacorps.com/components/com_comm.../font/jomsocial.woff you can dowload the font file

it can be caused by your 3rd party SEF component which avoid the font file, the solution is :
1. please you use original htaccess from joomla
2. disabled htaccess
3. disabled the redirection to community.html

thank you

fantastic! could the fact that I upgraded JS and didn't purge the sh404sef urls an issue? Both sites are using the same .htaccess which is Joomla's version with a couple of custom URLs not related to Joomla!

If I disable sh404sef, the font error goes away (so cryptic to say "font sanitizer") ... I have disabled and removed plugins until I was exhausted and did at one time disable sh404sef, but probably didn't give the fonts time to load/refresh from cache.

Hi Kevin,

Tbh..Since old times we always have problem with sh404SEF, maybe you can try with another SEF like AceSEF.

Actually this issue related with redirection / allowed open file via htaccess, if you contact sh404SEF developer I am sure they able to help it.

thank you