data-protection

47 Commits

10 Branches

0 Tags

1.3 MiB

Tree: d6f9d134fd

Commit Graph

Author	SHA1	Message	Date
Jairo Llopis	3cea2e1329	[IMP] pre-commit run	4 years ago
Jairo Llopis	517bee89f4	[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
Jairo Llopis	4bff063f1b	privacy_consent: Privacy explicit consent tracking tools (#11 )	7 years ago

Author

SHA1

Message

Date

Jairo Llopis

3cea2e1329

[IMP] pre-commit run

4 years ago

Jairo Llopis

517bee89f4

[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

Jairo Llopis

4bff063f1b

privacy_consent: Privacy explicit consent tracking tools (#11 )

7 years ago

3 Commits (d6f9d134fd0fee36a951600233db6e63d4f75d30)