Font Files

Follow this tutorial to enable your font files to be accessible via your member portal.

Updated over a week ago

Are your fonts not showing up in the member portal and/or you're seeing an error message in the console? Follow this tutorial to enable your font files to be accessible via your member portal.

If your fonts aren't showing up on your member portal, please make sure the following are in place:

  • Your font files are an absolute URL meaning it's https://yoursite.com/fonts/font.ttf and not /fonts/font.ttf in your stylesheet

  • Your .htaccess file is setup to allow sub-domains

When you're adding your member layout to PeopleVine, check to make sure that the css files you are importing are referencing the font file with an absolute URL, meaning it starts with https:// followed by the domain name, the folder path and the file name. If you are seeing relative paths, where they typically start with / or ../ or mainly without the https:// then you will need to setup the CSS record in the the layout's CSS.

If you are seeing an error message in your browser related to the font file, then you will need to update your WordPress or web server's settings in order to enable it.

In the event you see a CORS policy on a sub-domain such as https://members., then you can update your .htaccess file to include sub-domains as such:

# Allow font assets to be used across domains and subdomains<FilesMatch "\.(ttf|otf|eot|woff|woff2)$"> <IfModule mod_headers.c> Header set Access-Control-Allow-Origin "*" </IfModule></FilesMatch>
Did this answer your question?