Tahoma fonts ?

Doug G.
131 Posts
Doug G. posted this 17 January 2020
Ask a Question

Just noticed in the newest version that a LOT of the original bundled fonts are missing. Tahoma is just one of them.

Another issue, I can use the Tangerine fonts just fine inside the desktop, but when uploaded to the web it says the page is missing and falls back on Verdana.

Just noticed in the newest version that a LOT of the original bundled fonts are missing. Tahoma is just one of them. Another issue, I can use the Tangerine fonts just fine inside the desktop, but when uploaded to the web it says the page is missing and falls back on Verdana.
joomla fonts
Vote to pay developers attention to this features or issue.
13 Replies
Order By: Standard | Newest
Support Team
Support Team posted this 20 January 2020

Hi,

Nicepage loads fonts from Google Fonts library where Tahoma font is not available.

Another issue, I can use the Tangerine fonts just fine inside the desktop, but when uploaded to the web, it says the page is missing and falls back on Verdana.

For some reason, this font cannot be loaded. Please provide the link to the problem website so we can check this issue.

...................................................
Sincerely,
Olivia
Nicepage Support Team

Please subscribe to our YouTube channel: http://youtube.com/nicepage?sub_confirmation=1
Follow us on Facebook: http://facebook.com/nicepageapp

Hi, Nicepage loads fonts from Google Fonts library where Tahoma font is not available. > Another issue, I can use the Tangerine fonts just fine inside the desktop, but when uploaded to the web, it says the page is missing and falls back on Verdana. For some reason, this font cannot be loaded. Please provide the link to the problem website so we can check this issue. ................................................... Sincerely, Olivia Nicepage Support Team Please subscribe to our YouTube channel: http://youtube.com/nicepage?sub_confirmation=1 Follow us on Facebook: http://facebook.com/nicepageapp
Doug G.
131 Posts
Doug G. posted this 20 January 2020

Here is the error message as shown in chrome using F12 to bring up the developer screen.

01202020TangerineFontsDoNotLoad01.png

Another section of the views in the developer screen.

01202020TangerineFontsDoNotLoad'.png
Here is the error message as shown in chrome using F12 to bring up the developer screen. !01202020TangerineFontsDoNotLoad01.png! Another section of the views in the developer screen. !01202020TangerineFontsDoNotLoad'.png!
01202020TangerineFontsDoNotLoad'.png
01202020TangerineFontsDoNotLoad01.png
s-pike
12 Posts
s-pike posted this 20 January 2020

Try to replace font link in the <head> on link href="https://fonts.googleapis.com/css?family=Tangerine:400,700&display=swap" rel="stylesheet"

Try to replace font link in the `<head>` on `link href="https://fonts.googleapis.com/css?family=Tangerine:400,700&display=swap" rel="stylesheet"`

Last edited 20 January 2020 by s-pike

Doug G.
131 Posts
Doug G. posted this 20 January 2020

What css file do I need to edit. It isn't specific in the developer window.

Use the symbol to the right of the quote sign above and re-paste your code. It got translated and garbled

What css file do I need to edit. It isn't specific in the developer window. Use the symbol to the right of the quote sign above and re-paste your code. It got translated and garbled
Doug G.
131 Posts
Doug G. posted this 21 January 2020

Editing the JSON files to reflect the new settings didn't take.

So I need to wait for Oleg to fix it

Editing the JSON files to reflect the new settings didn't take. So I need to wait for Oleg to fix it
Doug G.
131 Posts
Doug G. posted this 21 January 2020

Olivia,

link:
incocosm.org

Olivia, link: incocosm.org
Doug G.
131 Posts
Doug G. posted this 21 January 2020

Olivia,

The plugin on the site displays the Tangerine fonts correctly, but the live site doesn't show any change in the fonts displayed. Note: Site cache cleared and browser cache cleared prior to home screenshot. I'm aware not doing this will/can result in the changes not being shown immediately.

Editing the page online shows:

01202020TangerineFontsDoNotLoad03.png

Home Page view shows: Note: Site cache cleared and browser cache cleared prior to screenshot

01202020TangerineFontsDoNotLoad04.png

Olivia, The plugin on the site displays the Tangerine fonts correctly, but the live site doesn't show any change in the fonts displayed. Note: Site cache cleared and browser cache cleared prior to home screenshot. I'm aware not doing this will/can result in the changes not being shown immediately. Editing the page online shows: !01202020TangerineFontsDoNotLoad03.png! Home Page view shows: Note: Site cache cleared and browser cache cleared prior to screenshot !01202020TangerineFontsDoNotLoad04.png!
01202020TangerineFontsDoNotLoad03.png
01202020TangerineFontsDoNotLoad04.png
Doug G.
131 Posts
Doug G. posted this 21 January 2020

Finally applied something of a kluge into the site settings, CSS tab. It was the only CSS input field where the @ wasn't stripped out. But this is the CSS I derived from 

https://fonts.googleapis.com/css?family=Tangerine:400,700

/* latin */
@font-face {
font-family: 'Tangerine';
font-style: normal;
font-weight: 400;
src: local('Tangerine Regular'), local('Tangerine-Regular'), url(https://fonts.gstatic.com/s/tangerine/v11/IurY6Y5j_oScZZow4VOxCZZM.woff2) format('woff2');
unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}
/* latin */
@font-face {
font-family: 'Tangerine';
font-style: normal;
font-weight: 700;
src: local('Tangerine Bold'), local('Tangerine-Bold'), url(https://fonts.gstatic.com/s/tangerine/v11/Iurd6Y5j_oScZZow4VO5srNZi5FN.woff2) format('woff2');
unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}
Finally applied something of a kluge into the site settings, CSS tab. It was the only CSS input field where the @ wasn't stripped out. But this is the CSS I derived from https://fonts.googleapis.com/css?family=Tangerine:400,700 /* latin */ @font-face { font-family: 'Tangerine'; font-style: normal; font-weight: 400; src: local('Tangerine Regular'), local('Tangerine-Regular'), url(https://fonts.gstatic.com/s/tangerine/v11/IurY6Y5j_oScZZow4VOxCZZM.woff2) format('woff2'); unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD; } /* latin */ @font-face { font-family: 'Tangerine'; font-style: normal; font-weight: 700; src: local('Tangerine Bold'), local('Tangerine-Bold'), url(https://fonts.gstatic.com/s/tangerine/v11/Iurd6Y5j_oScZZow4VO5srNZi5FN.woff2) format('woff2'); unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD; }
Support Team
Support Team posted this 23 January 2020

Hi,

The 403 is a permissions error. And usually, this is a server-side problem. The original link to the font uses HTTPS protocol. It looks like it causes problems on your server. We suggest that you either check the server secure politics or ask your hosting provider about this issue. This may help.

...................................................
Sincerely,
Olivia
Nicepage Support Team

Please subscribe to our YouTube channel: http://youtube.com/nicepage?sub_confirmation=1
Follow us on Facebook: http://facebook.com/nicepageapp

Hi, The 403 is a permissions error. And usually, this is a server-side problem. The original link to the font uses HTTPS protocol. It looks like it causes problems on your server. We suggest that you either check the server secure politics or ask your hosting provider about this issue. This may help. ................................................... Sincerely, Olivia Nicepage Support Team Please subscribe to our YouTube channel: http://youtube.com/nicepage?sub_confirmation=1 Follow us on Facebook: http://facebook.com/nicepageapp
Doug G.
131 Posts
Doug G. posted this 23 January 2020

Olivia,

You're not thinking it through.

The plugin on the site displays the Tangerine fonts correctly, but the live site doesn't show any change
in the fonts displayed. If I can use the plugin to edit online and the Tangerine fonts are displayed
properly until it is saved.

Take note: The Plugin (operating online) shows the Tangerine fonts correctly. But not after it is saved, the website refers back to a Sans font.

So the issue lies between the design side and the export logic. Otherwise the plugin would have the same problem with the fonts the website has. They are both running on the same hosting platform and site. This eliminates the host as a problem.

It should be logical that when the plugin is in design mode and the fonts are displayed properly. But after saving the file and the fonts now don't display, the error must lie in the save/export function where it goes from working to a 403 error.

Olivia, You're not thinking it through. > The plugin on the site displays the Tangerine fonts correctly, but the live site doesn't show any change > in the fonts displayed. If I can use the plugin to edit online and the Tangerine fonts are displayed > properly until it is saved. Take note: The Plugin (operating online) shows the Tangerine fonts correctly. But not after it is saved, the website refers back to a Sans font. So the issue lies between the design side and the export logic. Otherwise the plugin would have the same problem with the fonts the website has. They are both running on the same hosting platform and site. This eliminates the host as a problem. It should be logical that when the plugin is in design mode and the fonts are displayed properly. But after saving the file and the fonts now don't display, the error must lie in the save/export function where it goes from working to a 403 error.
Doug G.
131 Posts
Doug G. posted this 23 January 2020

Resolved in 2.5.1

Resolved in 2.5.1
michal84
143 Posts
michal84 posted this 31 May 2020

Hello all,
unfortunately I still experience the 403 error when loading Verdana, Robot and even Sans Serif fonts.
Is there any way, how to resolve, and not to delay page loading? See attachment.

Thanks for your answer,
Michal

Hello all, unfortunately I still experience the 403 error when loading Verdana, Robot and even Sans Serif fonts. Is there any way, how to resolve, and not to delay page loading? See attachment. Thanks for your answer, Michal
403-error-fonts.png
Doug G.
131 Posts
Doug G. posted this 31 May 2020

Not true. I've posted how I got around the font issue above. You will have to go to Google, find the font in order to find the address you need to plug in as I did. I placed the code in a hidden HTML block on the header. But, you shouldn't need to use it..A recent update was supposed to change from cloud font use storing the fonts locally.

If you aren't on the current version, update it. If you are, report this directly to Support along with everything you have tried to mitigate the issue.

Not true. I've posted how I got around the font issue above. You will have to go to Google, find the font in order to find the address you need to plug in as I did. I placed the code in a hidden HTML block on the header. But, you shouldn't need to use it..A recent update was supposed to change from cloud font use storing the fonts locally. If you aren't on the current version, update it. If you are, report this directly to Support along with everything you have tried to mitigate the issue.
You must log in or register to leave comments

Company
Product
Themes & Templates
Nicepage
Web Design