karlemilnikka

Thanks! I’ll keep an eye on the changelog.

Hi @wfpeter.

Thank you very much. If they wonder why I miss the old button, it’s for accessibility reasons.

Best regards
Karl Emil Nikka

I’ve updated the snippet to work with FluentCRM 2.7.40. The filter got renamed without any mention of it in the changelog. https://github.com/karlemilnikka/Useful-snippets/blob/main/opal_fluentcrm_google_fonts_fix.php

Absolutely. Thank you.

Hi @keraweb. Thanks for following up. Not yet. It has happened once again, but I still don’t know what caused it.

Switching status back to not resolved after plugin developer incorrectly set it to resolved for the third time.

Thanks. I read the changelog and there was no mention of any GDPR compliance improvements or changes to font handling.

I’ve checked the new version and it’s a step in the right direction. This fix is however currently not working at all. If you want to solve the web-view the same way I did (which is more of a workaround), you need to change line 1086 in ExternalPages.php from

$content = str_replace('https://fonts.googleapis.com/css2', 'https://fonts.bunny.net/css', $content);

to

$content = str_replace('https://fonts.googleapis.com/css', 'https://fonts.bunny.net/css', $content);

The 2.7.40 update doesn’t address the fonts in the emails (just the web-view). Check my Github snippet for more info.

Hi @tahmidulkarim.

That’s great! Do you have an ETA for when the compliant version will roll out?

Thanks, both for passing the feedback on and for providing such an excellent plugin/service.

It doesn’t look like they’ve added support for WP-2FA to their login form. They can however do so if there’s interest for it, so please consider reaching out to the developers of Download Manager Pro.

(Just to avoid confusion, I’m not in any way related to the developer of this plugin.)

Which plugin are you using on your custom login page for handling logins? Woocommerce’s and Uncanny Owl’s login forms are compatible, but other forms might not be.

I wrote a small workaround-snippet to use while waiting for an official solution.

Keep in mind! This is an unofficial workaround. Do NOT use it on a live site without rigorous testing for your specific site. Feel free to report any issues on Github.

Hi @tahmidulkarim.

I see. Thanks for the reply.

The font issue persists with the 2.7.1 release. Do you have any ETA for when it will be addressed, @tahmidulkarim?

I’ll leave a review when the product is a little more mature. Based on all the update issues we’ve had for the past couple of months, it doesn’t feel like a stable plugin yet so my review wouldn’t be fair.