Tree: 29cc32b1e6

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 '29cc32b1e6'

${ noResults }

Commit Graph

8 Commits (29cc32b1e67545a533df96542c9f880fec2f9edd)

Author	SHA1	Message	Date
OCA-git-bot	3c2f41264d	privacy_consent 12.0.1.1.2	3 years ago
OCA-git-bot	f1522f9d96	privacy_consent 12.0.1.1.1	4 years ago
OCA-git-bot	124f2faabe	privacy_consent 12.0.1.1.0	4 years ago
Jairo Llopis	a04df43828	[FIX] privacy_consent: make it work, basically Some little nasty details were overlooked in the v12 migration, which rendered the module basically useless: - The wizard used to ask for consent in manual activities did not fill the placeholders, resulting in an awkward UX. - The sent mails **did not have the token** to authenticate and actually allow accepting or rejecting. These buttons returned a 500 error. - Once the token is added, the form was ugly. - Sadly, some tests were testing the how and not the what. It is understandable due to the complexity of testing the what, even more without the `Form` utility, new on v12. These are fixed now too. @Tecnativa TT25868	4 years ago
OCA-git-bot	fa9fb53869	privacy_consent 12.0.1.0.1	4 years ago
Jairo Llopis	dda48f6fad	[MIG] privacy_consent: Migrate to v12 - Partner's `opt_out` no longer exists. Using `mail.blacklist` now. - Tests updated to support that change. - Test workarounds removed. - Duplicated-field-name-in-model warning removed. - Use create multi where possible.	5 years ago
fkantelberg	0f2ef1b796	Migrate privacy_consent to v11	5 years ago
Jairo Llopis	85274cd1ca	privacy_consent: Privacy explicit consent tracking tools (#11)	6 years ago