Missing Data Protection Directive page

[richwingerter]

Thanks for your help. I used a service to create a GDPR page and put in the right settings to get it. I also updated language in three of the EN.php files, one each in:

account/languages/
modules/form/languages
modules/news/languages

I don't think I'll ever need the third one, but the others will probably be necessary.

I changed DSGVO to: 'By submitting this form, I confirm I have read and agree to the <a href="%s" target="_blank" rel="noopener">Data Protection Directive</a>.'

I'm still testing, but this text now appears on the Sign_up page and the new privacy policy page displays if you click the Data Protection Directive link.

Your help is much appreciated.

[dbs]

Yes, you must first create such a GDPR page.
WB will then give you the option to select this page for the form or registration.
The content of this page is your "problem". There is no standard content.
The content depends on the content of your whole website. There are many GDPR generators to find, use them, but know what you need.

[richwingerter]

Dbs, thanks for that. I tried checking off the second checkbox. However, during sign up, I still get a broken link for the Data Protection Directive page:

I confirme, that i have read and agree to the <a href="https://testing.greenmaking.com/pages/home.php" target="_blank" rel="noopener">Data Protection Directive</a>  by submitting the form

Instead of an href to the directive page, I get an href to my home page.

It looks to me like I need to set this on the "Frontend Login, Signup, General Data Protection" page you mentioned in the "Data Protection Url" section. That implies I should create a page for it on the site, so that I can pick it from the list. Are there instructions anywhere for what should be on this page? If not, can I get something from a standard EU site for this?

I haven't gotten to the other two issues, but I appreciate your references on them.

[dbs]

Hi,

first point: you have  checked the second box in WB Settings > Frontend Login, Signup, General Data Protection?
In 2.12.2 seems the first two checkboxes have the same label "Activate for registration form".
The second is for form and should be checked in your case.

Second point: modules/form/languages/EN.php line 126

Third point: WB ROOT/languages/EN.php line 254|255|256

Hope it helps.

[richwingerter]

I just upgraded to 2.12.2. When I create a new user, I have some additional issues.

• The link to the Data Protection Directive page is blank. How do I enter the link?
• I'd like to change the wording of the confirmation line on the Sign-up form. What's the best way to do that?
• I want to change the wording of the initial e-mail message sent to new users, but I don't know how to change that text. What's the best way to change the standard text for this message?

The Sign-up page says:

I confirme, that i have read and agree to the Data Protection Directive by submitting the form

I'd prefer:

By submitting the form I confirm I have read and agree to the Data Protection Directive.

(Where "Data Protection Directive" is a proper link to the directive.)

I think this wording is easier for English readers to understand (and it fixes a couple typos).

I'd also like to reword the initial e-mail message to the user. Right now, it sends "Login name: xxxxx". I'd like to avoid this by sending a message like:

Your account at Green Making is now active. You can log in with the temporary password ----.

This avoids giving out the login name to someone who doesn't know it, but gives them the auto-generated password, so they can log in.

I'd also like to avoid the assumption the message was automatically generated and that they should delete it if it's in error. Instead, I'm going to just delete accounts after 48 hours if no one logs in. So, I'd prefer to replace those parts of the message with something appropriate for that, like:

If you did not create this account, please disregard this message. The account will be deleted after 48 hours if no one logs in."

Does anyone have advice how to address these issues?

[I previously had this under the wrong version.]