Sure, that makes sense. WordPress’ wp_remote_get() verifies SSL certificates by default.
Create a plugin and add this code to it, that should do it:
function troglos_disable_sslverify( $params, $url )
{
$params['sslverify'] = false;
return $params;
}
add_filter( 'http_request_args', 'troglos_disable_sslverify', 10, 2 );
Ok no error message now, but cannot detect the used fonts. Have tried with both manual and automatic.
Reverted to 3.8.3
What theme are you using? And are you by any chance using css minify/combine plugins, e.g. Autoptimize or WP Rocket?
I only use custom made lightweight themes. And no, while developing no Autoptimize or any cache are active.
Up to version 3.8.3 the only way to load fonts for me was manually pick them. No other enqueue method. Did I miss something? Should I declare the fonts somewhere, other than in the css?
Ah, there you go. So, Auto Detect didn’t work either in v3. 🙂 That’s a relief! 🙂
Yes, WordPress’ convention states that you should enqueue stylesheets (including external ones, like Google Fonts) with wp_enqueue_style(). OMGF goes through the enqueued stylesheets, to see if it contains any Google Fonts, whereas OMGF Pro scans the entire document, including @import and @font-face rules in inline stylesheets. It doesn’t scan through stylesheets (yet), though.
Btw. I’m working on a separate add-on for OMGF, which’ll bring back the custom font installer.
Ok now it’s clear.
I’ve added wp_enqueue_style() and it works with the new version.
Thanks for the quick reply