June 15, 2017 at 9:30 pm #8866
I purchased the Bryant font and used this program to add to WordPress. It’s not displaying on most devices except for the 2 that have the font saved locally to the computer. I have uploaded multiple versions of the fonts and tried each but without success. I checked the stylesheet that loads for the site (via the code inspector of Chrome and Firefox) and the fonts show up in the uaf.css file but still not displaying properly.
Please advise.June 16, 2017 at 6:12 pm #8871
The problem here is that your server is not allowing to load the fonts files to the browser. If you check this font url it says it is removed or doesn’t exists. http://ohnaturel-com.azurewebsites.net/wp-content/uploads/useanyfont/170612061643bryant-bold.woff
so, can you please keep this in your htaccess file and try ? The above link will not give such error when fixed.
<FilesMatch "\.(ttf|otf|eot|woff|css)$"> <IfModule mod_headers.c> Header set Access-Control-Allow-Origin "*" </IfModule> </FilesMatch>
If this doesn’t work, please ask your host provider to enable font (woff and eot format) for loading.
June 19, 2017 at 4:05 pm #8884
- This reply was modified 1 week, 2 days ago by Dinesh.
thanks for the response. I updated the .htaccess file with the the code you provided but I still have the same issue including the error message you pointed out concerning the .woff font file. However, when I viewed the following font file, I was able to download it: http://ohnaturel-com.azurewebsites.net/wp-content/uploads/useanyfont/170612061643bryant-bold.eot
Do you still believe that the server settings may need to be updated? I don’t have access to the server myself so I’m relying on the client to be able to make the updates.June 20, 2017 at 4:13 pm #8899
It is still not resolved. The main font files is woff version (used by all browsers except older IE). http://ohnaturel-com.azurewebsites.net/wp-content/uploads/useanyfont/170612061643bryant-bold.woff . This url is still blocked.
If htaccess entry is not working, then i think it should be redirected to support team to enable it.
ThanksJune 22, 2017 at 3:25 pm #8915
I was able to resolve the issue by adding code in the .webconfig file as outlined here.June 23, 2017 at 3:53 pm #8923
Glad you fixed and thank you so much for sharing here.