After Update: In firefox 26 font face broken

Hi,
I deactivated and deinstalled WP Supercache Plug In
Cleared Firefox cache
restartet and reloaded http://medientanz.de many times
no effect
firefox font face are still broken
Any ideas? Everything was OK with firefox before hat update, maybe it is a new code in that 2.53 enfold version?

thomas

Hi,
I updated to 2.5.4 and put the fontssquirrel fix in .htacess.
Then I cleared the firefox Cache, emptied and deaktivated the wordpress Cache Plugin.
Restartet firefox several times.
But – font- face still broken..

http://medientanz.de
firefox 26 win 8.1

Any idea? Thanks

Thomas

Hi,

Got base.css Version 10.02.2014 from Themeforest enfold Theme
Updated to css folder

No effect
firefox font-face still broken

hop you can help.Thanks
Thomas

Hi Dude,
I tried your recommondation and added all between

. <IfModule mod_mime.c>…
…
…
</IfModule>
to .htacess

I and emptied all caches.No font face in Firefox!
Than I deleted the Enfold whole folder and re – installed Enfold with todays newest Themeforest version
No font face!

Everything was working fine with the 2.50 enfold version: Font face was visible in Firefox
So it must be a code – changing in enfold after this 2.50???
Is it possible to get the old 2.5 Version? Where can I get it ? I would try to reinstall the 2.50 Version!

Thanks Thomas

Hi Dude,

I have tried several htacess solutions

the htacess <FilesMatch “.(ttf|otf|eot|woff)$”>
<IfModule mod_headers.c>
Header set Access-Control-Allow-Origin “*”
</IfModule>
</FilesMatch>
is not working for 2.54

1. With the enfold 2.50 Version, everything was OK.
2. After updating to 2.54 , font-face in firefox was broken
3.It must be a code changing in the enfold theme

Is it possible to re – download the 2.5 Version from somewhere? I want to reinstall this working version

Thanks
Thomas

Thanks dude,

you can check the problem here:

http://medientanz.de

in Firefox 27 :Broken search button in header etc…

What I have done for testing:
Reinstalled firefox.
Tested several htacess solutions
Deaktivated all plug ins
Emptied the browser cache
Deleted the whole enfold folder and reinstalled it
Tested the pure Enfold Theme ( without the Enfold- Child Theme)

1und1.de Server

Hi,
What I have done to solve the Problem with font face:

1. I tried to deaktivate alllplug-ins.

2. and added to .htacess:
AddType application/vnd.ms-fontobject .eot
AddType font/ttf .ttf
AddType font/otf .otf
AddType application/x-font-woff woff
<FilesMatch “\.(ttf|ttc|otf|eot|woff|font.css)$”>

<IfModule mod_headers.c>
Header set Access-Control-Allow-Origin “*”
</IfModule>
</FilesMatch>

3. and to child css:
@font-face {
font-family: ‘entypo-fontello’; font-weight: normal; font-style: normal;
src: url(‘http://medientanz.de/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/assets/fonts/entypo-fontello.eot?v=2&#8217;);
src: url(‘http://medientanz.de/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/assets/fonts/entypo-fontello.eot?v=2#iefix&#8217;) format(’embedded-opentype’),
src: url(‘http://medientanz.de/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/assets/fonts/entypo-fontello.woff?v=2&#8217;) format(‘woff’),
src: url(‘http://medientanz.de/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/assets/fonts/entypo-fontello.ttf?v=2&#8217;) format(‘truetype’),
src: url(‘http://medientanz.de/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/assets/fonts/entypo-fontello.svg?v=2#entypo-fontello&#8217;) format(‘svg’);
}

No effect! Font face fonts still broken
fonts are broken in firefox and in iexplorer (with chinese symbols!!!!),
Chrome and Safari are OK!

4. And I have done a little test: I uploaded an own fontello font zip: This own font is working in all browsers!

but i need the working font face fonts! (search button etc)

And again: With the older version, 2.50 there was no problem with font-face.
Is there a theme update in the pipeline to solve that problem?

http://medientanz.de

Thanks! Thomas

Thanks Robin, I think it´s the same problem. Hope it will be fixed in 2.5.5 …
Thomas