Does not work on local environment

Hi!

I know I promised before to disable SSL verification, but after researching it a little I decided against it, because simply put: it’s a security issue, and to create a whole option for it to toggle it seems excessive. Especially since people will only run into this on local (non-SSL) environments).

So, you can do 1 of the following:

1. Create a self-signed SSL certificate, or
2. Create a plugin which disables SSL verification like so:

function disable_sslverify($params, $url)
{
    $params['sslverify'] = false;

    return $params;
}
add_filter('http_request_args', 'disable_sslverify', 10, 2);

Hope it helps!

• This reply was modified 3 years, 9 months ago by DaanvandenBergh.

ad 1.) self signed certificate does not work as stated above:
“OMGF encountered an error while downloading Google Fonts: http_request_failed – cURL error 60: SSL certificate problem: self signed certificate”

ad 2.) added your code with Plugin “Code Snippets”
a) does not work on “Laragon” with http => same error as before
“OMGF encountered an error while downloading Google Fonts: http_request_failed – cURL error 7: Failed to connect to wpt.test port 443: Connection refused”
b) does not work on “Local” with http => error message, but after refreshing the page found google fonts are shown, but … not downloaded
c) works in a crazy way on “Local” with self signed SSL certificate => error message, but after refreshing the page found google fonts are shown … and installed

That is interesting but nothing that I can use in a classroom for teaching WordPress in local environments. So I have to exclude OMGF from my lectures.

Anyway, thank You for your efforts.

Found a solution which works on http without any tricks:
https://www.ads-software.com/plugins/wrap-google-fonts/

Hi again,

I assume you don’t know how to create a plugin, since you used Code Snippets to add the code I provided for you. So I did it for you.

Copy the file in this Github repository to your wp-content/plugins/ folder and OMGF will work without any crazy stuff: https://github.com/Dan0sz/disable-sslverify

I develop OMGF on a local environment after all, so I know this’ll work ??

Tried your plugin:
a) with “save target as” from github => does not work (100kB file with a lot of github xyz crap)
b) copy code from github in texteditor ans saved as .php => 1kB file
=> works with the exact same results on “Laragon” and “Local” (two common local environments) as my test with “Code Snippets” (which usually works very well for such tests)

But you are right, I’m not a programmer and so I ask you, if you could take a look at the code of https://www.ads-software.com/plugins/wrap-google-fonts/ which works out of the box even on local http sites.
Maybe there is a solution in this other plugin for downloading Google fonts which could be integrated in OMGF?

Ok, yeah. Save target as…’ isn’t gonna work.

The 2nd method should work. Shame that it doesn’t work as expected.

I will take a look at that plugin’s code! Might learn a thing or two ??

Good luck with your lectures!

Hi again,

I looked into the plugin and there’s a few significant differences between OMGF and Google Fonts Wrapper.

1. OMGF uses Google Fonts Helper to fetch the fonts in different filetypes, and generates a stylesheet which is cross-browser compatible, whereas the wrapper simply copies the stylesheet from Google Fonts’ server upon the first request, along with the accompanied fonts. This means that only the version compatible with the browser making the first request is fetched, e.g. .woff2 on Chrome or Firefox, but .ttf on some mobile devices.
2. Google Fonts Wrapper uses native PHP functions to do the fetches (curl_exec()), whereas OMGF uses WordPress’ wp_remote_get() function, which essentially is a more secure wrapper for PHP’s native curl feature set.

At this point, I’m researching if I could modify its behavior based on what protocol you’re using. But nothing I can release short term I’m afraid.

Thanks for the heads up, though. Definitely should do something about this.

• This reply was modified 3 years, 9 months ago by DaanvandenBergh.
• This reply was modified 3 years, 9 months ago by DaanvandenBergh.
• This reply was modified 3 years, 9 months ago by DaanvandenBergh.