GDPR § 13 implementation into users registration #20261
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request for Issue [no issue created beforehand] .
GDPR will be in effect from may 25th, 2018.
One of the implications of this is, that a controller (see GDPR §4.7) is required to inform the 'data subject' about his/her rights regarding the collected personal data "at the time, when this data is collected" (see GDPR §13 https://gdpr-info.eu/art-13-gdpr/ ).
To help website administrators with this requirement, we could include a link to the respective "information article" in the registration form.
I implemented such a solution with this pull request (and am looking forward to discuss this).
Summary of Changes
com_users/views/registration/tmpl/default.php
4 and 5) provide nessessary language strings in backend and frontend
Testing Instructions
Go to "user administration" [Backend] and open the [Advanced] tab in the user configuration dialog
provide respective info in the last three (new) configuration fields
Goto frontend and register a new user:
Expected result
the link to the "information regarding GDPR §13" shows up before the submit button
clicking the link opens a new window with this information article
Actual result
currently there is no support in Joomla to deal with this new legal requirement (although a website admin could of course always circumvent this himself).
Documentation Changes Required