karlemilnikka

Thank you very much for the reply, @keraweb. I’m currently investigating if it could be a Redis cache issue. I’ll update the post if I find out anything.

The GDPR compliance issue persists in the 2.7.0 release. So does the currently incorrect statement about full GDPR compliance.

@gusdrummer They fixed the issue with 4.0.2, released just a couple of hours ago. astra_single_post_meta works again.

(I haven’t heard back from the support agents.)

@reteinformatica Oh. I didn’t know it required approval. Here’s a temporary direct link in the meanwhile: https://send.bitwarden.com/#I59onu9DwUqWEa-LAMpn3Q/nznTN-2L7QePel0NQc8ZRA.

Keep in mind that there’s a bug causing some of the changes to not be reflected in the live-preview. Uncheck the marked boxes, save the changes and reload.

@reteinformatica Join the Facebook group so that you can see the screenshot I posted. I cannot post images here.

You can fix this by unchecking the boxes in the blog post title design section. Here’s a screenshot if you have access to the Facebook group: https://www.facebook.com/groups/wpastra/posts/1511426599326599/?comment_id=1512240585911867&reply_comment_id=1512242829244976.

The UI seems to be unfinished so the changes aren’t shown in the live view (you need to save and reload). Astra’s custom selector design also mixes checkbox and radio button behavior, lacks descriptions and cannot be used with the keyboard alone (accessibility issue).

Issue fixed in Spectra 2.3.0.

Hi @mohsinbsf.

Thank you very much!

Thanks for the reply. Please keep it as unresolved until the patch is out and the issue actually is resolved.

Please stop incorrectly marking the issue as resolved until there’s a solution (or the part about 100?% GDPR compliance has been changed).

The Spectra developers have confirmed the issue in the official Facebook group. It will be addressed in the next update.

Thanks. And even better would be if Google Fonts were automatically loaded from the WordPress server. That would let everyone use Google Fonts without compliance issues.

This issue has incorrectly been marked as resolved (without an answer).

I found the action hooks to add custom stylesheets, so basically, we just need a filter to disable Google Fonts from emails and web views (similarly to the filters you already offer to disable incompliant tracking).

For bypassing readers, these are the actions hooks:

• fluentform_email_header
• fluentcrm_view_on_browser_head.

Thanks for the heads up, @wpuser2022. I realized that almost all five star reviews are from newly registered accounts with only one review each.