Bonaldi

Hi,

Why use a partial translation when the extension is 100% translated?

I’ll email you all the updated .js and .po files to integrate in the plugin, ASAP.

Regards.

It’s OK.
Thanks.

Actual version seems to be 2.83.20.

Hi,

Impossible to modify my review for the moment :-(, but the beta version I had access to audit it should bring the loading of Google fonts locally, as required by the European GDPR.
Following my alert, the reaction of the authors was quick and efficient.
I recommend the upcoming version of this theme.

Hi,
I don’t see any direct messages on wordpress.slack.
Are you sure you posted in the right place?
What login ID do you use?
I’ll message you on Blocksy’s site directly, if necessary..

Hi,
Glad to hear it.
Are you on wordpress.slack?
We can talk about it there.
I would be willing to help and test your GDPR compliance following your evolution.
Then I can raise my review to 5 stars and recommend your theme again. I’m looking forward to it.
Regards.

Hi,

I think the best method is to implement the WPTT scripts on GitHub : webfont-loader.

You have a sample implementation on the repo in the ExS theme.

Hope this helps!

Hi,

I’m glad to see that you recognize that the free version is not GDPR compliant.

Indeed, you can’t dump on Google and say that they are the ones who are not compliant: any operator who sets up collection means is co-responsible, according to the GDPR.

I will be happy to review my assessment once you have made the changes, be sure.

But do you have an example of a concrete use case that would pose a problem of backwards compatibility with the simple solution I described?

All the best.

Hello,

I repeat.
I never said it doesn’t work.
I said, in response to Eduard, It doesn’t HELP.

I don’t think you understand that I am ONLY talking about the FREE version as the WP guidelines require. You can’t say that this one has an option that makes it compliant since the option in question is not present in this version.

No offense, but I think you didn’t understand the GDPR legislation either.

As a professional specializing in GDPR compliance, I urge you to read the legal texts or have them explained to you.

Your information is wrong: the remote calling of Google policies has been condemned by the European control authorities.

The gist is that this transition is not an easy one and requires a bit of effort from our end to smoothly migrate pro users from the pro addon to the next solution.

The solution is very simple and quick to implement:
– Selects by default a system font in the font drop-down list.
– Place a checkbox (unchecked, GDPR opt-in obligation) “Enable Google fonts (not GDPR compliant)“, above the font dropdown list: the user can choose to embed them or not by checking the box, but he will have been informed beforehand of the legal risks (GDPR transparency obligation).
– the boolean of the checkbox will activate your snippet:

/** Unset remote Google fonts */
add_filter('blocksy:typography:google:use-remote', function () {
  return false;
});
add_filter('blocksy_typography_font_sources', function ($sources) {
  unset($sources['google']);
  return $sources;
});

That’s all.

I’m not trying to diminish your efforts, I’m being factual: the GDPR went into effect in June 2018, it’s time to put compliance in your priorities, from my point of view.
I furthermore wrote that Blocksy is a great theme and I really mean it.

• This reply was modified 2 years, 7 months ago by Bonaldi.

creativethemeshq – To help you, you can already read this:

https://make.www.ads-software.com/themes/2022/06/18/complying-with-gdpr-when-using-google-fonts/

@jdembowski

Duplicated here in the right post: Regarding the link to the wp.org position, OK. I had forgotten that they were not desirable in the reviews. Sorry, even though it was talking about wp.org’s position regarding Google fonts, you did the right thing by removing it.

Not really useful feedback.

Obviously I do not share this personal opinion.

Regards.

@creativethemeshq

I was just responding to the previous post. :
Hope this helps! > It doesn’t.

We do have an option that loads Google Fonts locally : I didn’t find it in the repo version. Could you tell me where it is in the theme settings in administration? If it exists, I will modify my review to put 5 stars.

The problem is that this option is not in the free version presented here… as you indicate on your site.

From an ethical point of view: the average user who doesn’t have the necessary technical knowledge is never informed that he/she is putting himself/herself in an illegal situation by selecting a Google font in the font drop-down list.

The fact that you have to use a plugin or a snippet to disable the call to the Google API shows that the theme itself doesn’t do it (in the free version).

To solve this problem, simply implement local loading of Google fonts in the free version or inform the user of the risk and make the plugin that does so available for free.

I am open to exchange on the subject if necessary.

Regards.

@jdembowski

I’m in the WP ecosystem since 2004, I know the rules and I never talk about Premium versions here, because I follow the guidelines.

Regarding the link to the wp.org position, OK. I had forgotten that they were not desirable in the reviews. Sorry, even though it was talking about wp.org’s position regarding Google fonts, you did the right thing by removing it.

Regards.

It doesn’t.

Hi,

Thanks for your quick answer.

Yes, I had seen the option, but it allows you to have a non-compliant site when you are a newbie without legal knowledge of the GDPR.

So it would be wise to remove it as soon as possible.

Regards.