Tree: 74c3f38e74

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 '74c3f38e74'

${ noResults }

Commit Graph

5 Commits (74c3f38e740f66e0eb4b176d739362e7d44e301b)

Author	SHA1	Message	Date
Jairo Llopis	9b23ee84da	[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	3 years ago
Jairo Llopis	ce673246d4	[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	0f6487f338	[IMP] pre-commit run	4 years ago
fkantelberg	83a3f60c79	Migrate privacy_consent to v11	5 years ago
Jairo Llopis	a79b9a1e78	privacy_consent: Privacy explicit consent tracking tools (#11)	6 years ago