[wp-trac] [WordPress Trac] #44043: Framework for logging/retrieving a users consent state

WordPress Trac noreply at wordpress.org
Mon May 21 19:54:40 UTC 2018


#44043: Framework for logging/retrieving a users consent state
------------------------------------+------------------------------
 Reporter:  cookiebot               |       Owner:  (none)
     Type:  enhancement             |      Status:  new
 Priority:  normal                  |   Milestone:  Awaiting Review
Component:  Privacy                 |     Version:  trunk
 Severity:  normal                  |  Resolution:
 Keywords:  gdpr 2nd-opinion close  |     Focuses:
------------------------------------+------------------------------

Comment (by xkon):

 @gisle nobody is going to force any new implementation on anyone. That's
 not how things are done and I'm sure you already know that.

 There was a discussion in a different ticket about Logging the consents
 etc so there was the need to create extra ones for a different 'scope' but
 on a similar matter.

 The idea is to see if we could create in core the functionality needed for
 plugins to check for any given consent and then act accordingly on loading
 or avoiding to load scripts etc.

 If we go forth with a consent logging mechanism ( and we probably will as
 it's needed ) there's no point of not doing an all around class that could
 take care of everything imho.

 So again it would be up to the user to 'use' any kind of plugin that
 accesses these functions to do whatever is needed to be done. If he
 doesn't want to well there's no change for him so @gisle that sorts your
 concerns about having extra 3rd parties etc. You don't have to if you
 don't like it, but the functionality has to be provided for whoever wants
 to use it as well.

 Now the only 'issue' let's say I see with this theory from the OP and I'm
 not sure I'm 100% with is this `Other plugins should be able to retrieve
 the users consent state ` I don't like giving access to all plugins on
 everything. As this could be easily exploited by some not so 'trusty'
 ones.

 It's the same principle as in logging we have to find a way that the
 consents are handle individually if possible or there's only 1 access
 somehow if that makes sense?

 For example if I say 'yes' to a 'marketing' cookie I wouldn't want that to
 be misused by another plugin and add 10 things more because I said yes to
 1 ( if that makes sense ).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/44043#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list