[Resolved] Typography (Font Family) issue in Firefox

Hi Tom,
Disabling all but the GP plugin made no difference.

Everything except the font family changes when adjustments are made.

All typography elements should appear using the “Impact” font family and in bold (Just for testing).

IE and Chrome display the page with the new font family correctly but not Firefox.

Finally generated a debug.log for you.

Made some changes in the Customizer to generate this.

Most of it was comprised of duplicate entries so here it is condensed:

[23-Feb-2016 15:17:54 UTC] PHP Notice: Undefined variable: generate_settings in /srv/www/vhosts/inthelink.com/httpdocs/wp-content/plugins/gp-premium/addons/generate-menu-plus/functions/generate-menu-plus.php on line 732

[23-Feb-2016 15:17:58 UTC] PHP Notice: Use of undefined constant GENERATE_VERSION – assumed ‘GENERATE_VERSION’ in /srv/www/vhosts/inthelink.com/httpdocs/wp-content/plugins/gp-premium/addons/generate-typography/functions/customizer/google-font-dropdown-custom-control.php on line 182

[23-Feb-2016 15:17:58 UTC] PHP Notice: Use of undefined constant GENERATE_VERSION – assumed ‘GENERATE_VERSION’ in /srv/www/vhosts/inthelink.com/httpdocs/wp-content/plugins/gp-premium/addons/generate-backgrounds/functions/controls.php on line 74

These are the 3 errors being generated repeatedly in the log.

Let me know if you need the entire log.

Thanks.

I had changed to Twenty-Sixteen as WordPress had suggested and must have sent you the log from when that occurred.

GP has been re-activated and will send you an updated log.

Here’s what I pasted in the wp-config this morning:

// Enable WP_DEBUG mode
define( ‘WP_DEBUG’, true );

// Enable Debug logging to the /wp-content/debug.log file
define( ‘WP_DEBUG_LOG’, true );

// Disable display of errors and warnings
define( ‘WP_DEBUG_DISPLAY’, true );

Rechecked it and the code is still there.

Since enabling the GP plugin there hasn’t been any error reporting activity that I’m aware of.

Changing the typography settings is not producing any screen errors or debug logs.

Perhaps I’ll have to use Chrome or IE to see the true styling of the site.

Firefox must be broken in some way.

Something that just occurred to me this morning while thinking about what’s different from the last build where everything worked perfectly and this current build where there’s issues.
The answer… Cloudflare.

The previous build’s web host couldn’t easily implement Cloudflare into it’s system so it was not used.

On this current build, Oone of their apps was causing a “mixed active content warning” for the HTTPS.
Only in Firefox.
IE and Chrome were fine.
Disabling the app resolved the issue.

One of their other apps could be the issue here as well.
This will be checked out ASAP and I’ll let you know.

If that fails to resolve it, then I’ll give you a login account.

Thanks Tom,
Mo

Hi Tom,
Found the culprit and it wasn’t what I expected.
It seemed that it would be more likely to be a Firefox add-on, them ore extension.

Turned out to be a simple setting under the Firefox “Content” option.

After installing Windows 10 in January, I had chosen to disable “Allow pages to choose their own fonts, instead of my selections above” setting in Firefox and, of course, completely forgot about the setting.

Unchecking it locked all fonts to what was chosen as the default for ALL webpages.
That being Arial.

Checking it allowed the typography settings from GP displayed to display properly.

Pretty much shot myself in the foot…

So nothing serious, only slightly embarrassing.

Something for future reference if anyone else ever has this “problem”.

Thanks for the support.

Awesome as usual!

Regards,
Mo