Hello,
we are using latest version of JA Seven Template Quickstart 1.1.0
In backend Template Settings - Site Settings - Typography - we have initially turned on
Google font and selected as follows:
Font Family: Alata
Heading: Font Family: Lobster Two
Navigation: Font Family: Alata
So far so good. Our site is looking as we want!
But according to the german laws and the strict data protection rules with GDPR,
we have been strongly advised to turn of Google fonts and to rather store the fonts locally
on our server as otherwise the site visitors IP will be transfered to Google when fonts are
being loaded from Google servers.
Therefore we have downloaded the same fonts to a subdirectory 'fonts/'
and used the 'Custom Fonts' in Templates Fonts Manager
and used 'Font CSS URL' to add the fonts.
This worked fine and we can see the fonts being listed in Font Manager
and have selected them accordingly in same way we did before but now with
Google Fonts turned off:
Font Family: Alata
Heading: Font Family: Lobster Two
Navigation: Font Family: Alata
But when we now check the site only the font for section 'heading' has been taken into
consideration while for the general webpage text and navigation there is still a seeded
standard font.
Interestingly when we check the website preview within the Template Style and Site Settings, we
can see the correct font 'Alata'
Is this a bug in the Template/Code ?
Why it is not working in same way as with Google Fonts enabled ?
Regards
Markus