Tree: 2f4ff19c09

10.0

11.0

12.0

12.0-personal_privacy_activity

13.0

14.0

15.0

8.0

9.0

oca_12.0

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '2f4ff19c09'

${ noResults }

Commit Graph

5 Commits (2f4ff19c093a3eea0ad625106f3d4d539d3ca090)

Author	SHA1	Message	Date
Jairo Llopis	4a5ba7cddc	[FIX] privacy_consent: ensure there's always a request user As the controller is `auth="none"`, sometimes there's no user. This wasn't a problem on v12 where `sudo()` applied `SUPERUSER_ID` by default (below, line 35). In v13 we need to add it manually to avoid some situations where `self.env.uid == False`. @Tecnativa	4 years ago
Jairo Llopis	8449b8e564	[MIG] privacy_consent: version 13.0 - Remove prefetching optimizations; v13 ORM does it better. - Reset counters always in computed methods. - Remove workaround for skipping duplicate consent creation message. - Implement the new `_creation_subtype()` to let creation subscriptions keep on working. @Tecnativa TT25941	4 years ago
Jairo Llopis	3cea2e1329	[IMP] pre-commit run	4 years ago
fkantelberg	c75a544c1e	Migrate privacy_consent to v11	6 years ago
Jairo Llopis	4bff063f1b	privacy_consent: Privacy explicit consent tracking tools (#11)	7 years ago