WPIntell

Source evidence

Fonts loaded through http instead of https

TK Google Fonts GDPR Compliant · support · 2016-08-03T12:36:00+00:00

mixedsentiment
mediumseverity
0.84relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 27 rows with source links

18.5% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

22 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
SjorsHijgenaar resolved
Hi all, The fonts are being loaded through http instead of https, creating errors on https environments. Is there a possibility this is fixed in future releases? You really only need to add the ‘s’. https://wordpress.org/plugins/tk-google-fonts/ Hi @sjorshijgenaar , I have uploaded a new version with https support. Cheers, Sven Hi Sven, Version 1.3.2 still contains a link to non-https URL. In file tk-google-fonts/includes/helper-functions.php line 27, I replaced ‘ http://fonts.googleapis.com’ ; to ‘//fonts.googleapis.com’. That worked for me. The whole file can be simplified because of (nearly) duplicated code: wp_register_style/wp_enqueue_style function calls in ‘selected_fonts’ loops. But that’s my opinion. Hi @akamp , this is definitely true and a great improvement. I will make sure it gets changed for the upcoming version. If you are willing to create a pull request of your changes would be a great help and speed up the process. https://github.com/Themekraft/tk-google-fonts Contributions are Welcome! 😉 Cheers, Sven

Comments

3 shown
Sven Lehnert 2016-09-26T10:30:00+00:00

Hi @sjorshijgenaar , I have uploaded a new version with https support. Cheers, Sven

akamp 2017-04-20T20:51:00+00:00

Hi Sven, Version 1.3.2 still contains a link to non-https URL. In file tk-google-fonts/includes/helper-functions.php line 27, I replaced ‘ http://fonts.googleapis.com’ ; to ‘//fonts.googleapis.com’. That worked for me. The whole file can be simplified because of (nearly) duplicated code: wp_register_style/wp_enqueue_style function calls in ‘selected_fonts’ loops. But that’s my opinion.

Sven Lehnert 2017-04-21T12:33:00+00:00

Hi @akamp , this is definitely true and a great improvement. I will make sure it gets changed for the upcoming version. If you are willing to create a pull request of your changes would be a great help and speed up the process. https://github.com/Themekraft/tk-google-fonts Contributions are Welcome! 😉 Cheers, Sven