WordPress.org

Ready to get started?Download WordPress

Forums

fontface fonts not working after redirecting domain (4 posts)

  1. Adria C.
    Member
    Posted 2 years ago #

    Hi all,

    I've made a website at http://bespokeberlin.de. In an effort to rank higher in the UK too, we've got a http://bespokeberlin.co.uk domain. I installed wp for the de domain, then put a redirect on the co.uk domain, so it points to the de directory. (hope this makes sense!)

    I decided on this configuration in an effort to reduce content duplication, since we want one website and two domains. (I guess I could also use some feedback if this is a worthwhile endeavor, if you feel so inclined...still not so sure it's a good idea.)

    The problem is that the @fontface fonts work fine, except on the first page of the uk site. If I go to http://bespokeberlin.co.uk, I get system default fonts, one click into the website (where it switches to the de directory), and all fonts are just fine.

    Any ideas on how to fix this? Help would be greatly appreciated!!!

  2. Adria C.
    Member
    Posted 2 years ago #

    Update: I found this article that could help me, but I still can't quite get my head around it, and how to apply it to my situation:
    http://www.lowest-common-denominator.com/2010/01/http_access_control_to_multipl.php

    I'd like to try what they suggest, but don't know exactly how to edit the code they say to add to the .htaccess file:

    <FilesMatch "\.(eot|otf|woff|ttf)$"> SetEnvIf Origin » "^http(s)?://(.+\.)?(domain1\.org|domain\.com)$" origin_is=$0 Header always set Access-Control-Allow-Origin %{origin_is}e env=origin_is </FilesMatch>

    I tried adding this to the end of the file inside the de directory:

    <FilesMatch "\.(eot|otf|woff|ttf)$">
     SetEnvIf Origin »
     "^http(s)?://(.+\.)?(bespokeberlin.co.uk|bespokeberlin.de)$" origin_is=$0
    Header always set Access-Control-Allow-Origin %{origin_is}e env=origin_is </FilesMatch>

    But it didn't work...

  3. Adria C.
    Member
    Posted 2 years ago #

    Well, crap.

    I tried some other things, can't even remember exactly what, with the .htaccess file. It created an internal server error, so I tried to upload the original that I saved, and it's not working at all now!

  4. Adria C.
    Member
    Posted 2 years ago #

    Sorry, this is getting silly. All's well, internal error fixed.

    Still not getting my @fontface fonts, though...

Topic Closed

This topic has been closed to new replies.

About this Topic