EEConf 2024 is around the corner! EEConf 2024
If you have all CP consents for the logged in person set to status No you get a warning:
> In order to use all features of Control Panel, please opt in Functionality Cookies consent.
Is there a list of features that don’t work unless you have allowed CP Functionality cookies?
That does beg the question that CP features shouldn’t rely on Functionality cookies to work, they’d be necessary/required cookies or fair usage?
That should be for front end only according to the field notes? At least that’s how I read/interpret it!
This seems to be an issue when you need different consents for front end (visitor) and back end (site authors/admins). I had a client raise this, they couldn’t understand why you had to accept additional cookies to use specific features - they’ve already logged which sets a cookie in so why is it needed?
It’s problematical because not accepting CP Functionality cookies means you can’t use certain (undetermined as yet) features unless you do. Perhaps there is some PII being referenced in CP Functional cookies?
I might be going mad with this one but it’d be good to know the why’s and wherefore’s of the logic.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.