Hi @pinchies
This is a re-consent screen. It shows up for logged in users that haven’t agreed to the privacy policy.
This screen has minimal styling to use the activated Theme styling. That might be one reason why it may look ugly on your theme.
But still, even with the proper styling, other users reported that this screen is too obtrusive.
I’m currently working on the next major release (v2.0) that will change this flow to something more subtle. It will be a notification bar, similar to the current privacy bar. That notice will state that the policy has been updated. Will have a link to the policy page and a button to accept it.
I hope that when that version gets released, that you could take a second look at it and update your review.
That release is scheduled for Tuesday, May 22.
I don’t think the overlay looks ugly at all.
It’s basic, but with my theme, it looks just fine.
It’s functional and does exactly what it needs to.
Look forward to seeing V2.0 though.
This plugin is making GDPR compliance very easy!
I’ll definitely revisit my review once the new version is out – I can see a lot of promise, but this GDPR policy nightmare needs real clarity, not more confusion for us stressed devs. I wish you every success with the plugin, I understand this is a 11th hour dash!
Personally, I would like the option to be able to disable the privacy policy notifications.
-
This reply was modified 6 years, 12 months ago by
pinchies.
Disabling them would be against GDPR. But hey, if you really want to, deselecting the privacy policy page from the plugin settings will make this screen go away. We will no longer track that page for updates.
I don’t think I understand the need – because visitors are never presented the privacy policy in the first place? But if it has to be re-presented for GDPR compliance, then I really think it should be no more intrusive than the consent overlay, presented in the same style would be good for consistency.
It is also *essential* that if the notifications are going to be presented, then the update checking is 100% rock solid reliable, and not generating false notifications. This was my biggest complaint – I suspect something happened in my testing that triggered it even when I had not changed anything on the privacy policy page. Making the change notifications always requiring priority manual approval on the backend would be my preference. Minor typo corrections should not automatically trigger a policy change.
Well… I guess you could disable them and still be compliant. All you really have to do is notify your users somehow. An email perhaps?
When you update your policy you get a notice in the dashboard. One blue button says “ask for re-consent” and the other says “ignore”. That is the case if it was just a typo you don’t trigger the notification again.
Thats what I thought was supposed to happen – but unfortunately I saw the white change notification, and I never clicked either of those buttons.
@pinchies – you will have seen the overlay as you were probably logged in as admin, installed the plugin and then visited a page on the front end.
The policy shows as you hadn’t already accepted the terms, as your admin account was created BEFORE you installed the plugin.
Once accepted, you won’t see it again unless the policy is edited and the reconsent button pressed.
Ok, that sounds like it was working correctly then – my mistake. However, I am using it on a site that is public facing, and the logged in users are all editors who are not the ones that need to see the terms.
I am still confused why I was shown the big modal white “terms have changed” screen, and not just the regular neat black consent overlay bar.
The only reason is that you were logged in, and this modal sits on top of the bar. The bar was there, but it was sitting behind it.
Like I’ve said, if you deselect the privacy policy page from the settings, this screen will go away. You can then notify your users in a different way.
At least until V2.
Thanks for taking the time to explain the operation of this feature. I think I’m getting it, and I appreciate your time.
My final question would be regarding caching plugins – have you done testing, and/or can you recommend any caching plugins that are compatible with this plugin?
-
This reply was modified 6 years, 12 months ago by pinchies.
-
This reply was modified 6 years, 12 months ago by pinchies.
You are welcome.
Caching plugins can be an issue. I’ve done some changes over the weeks to mitigate this but they can be an issue if not properly configured.
For the most part, all the support tickets I used to get regarding caching went away. It’s been a long time since someone reported anything related to caching.
One thing about caching is that you may not use the PHP version of the is_allowed_cookie or has_consent functions. You will have to use the javascript version.
That’s because the PHP result of your IF statement could be cached, then even if I am not agreeing to something anymore, your cached version still thinks I do.
Other than that, I haven’t received any more support requests on this. So I’m assuming it is working.
