FrontendLoginRegister - A configurable module for fast implementation of an user management system based on FrontendForms

[marie.mdna]

Hi @Juergen, thank you for this very fast reply ! I have access to phpmyadmin and already checked it but can't seem to find any remaining "fl_registerpage" after clearing the project from all related files from the backend and by checking around.

However, I have tried to restart a fresh project and didn't face any error, I guess that I will simply spare you the trouble and start again from this version !

[Juergen]

Ok, fine that it works on the second run ?. Sometimes something mysteriously happens and you are not able to reproduce it or trace the problem to its source.

The "fl_registerpage"  must be an entry inside the table "templates". If id does not longer exist, everything should be fine!?

[Frank Vèssia]

Hey Juergen, great module!! I just discovered it and I'm trying to implement it in one of my websites.
Few things if I may:
- I can't find the submit button texts inside translation files.
- Is there a way to choose the position of the privacy check inside the form? right now it appears on top of everything when usually is at the end. Also I have an external privacy policy but in settings I can only choose an internal page.
- I have few input fields text inside my user template (name, surname, age, ecc..) but they don't show up on the settings select
- Since my website is also an app for Android and iOs, the app stores ask for a public account deletion link but your system is a private page for the already logged in user. In my other websites I have a form where user can put the email and if the email exists it sends a confirmation via email.

Edit: I added a captcha and now the privacy check is at the bottom 🙂

[Juergen]

Hello @Frank Vèssia

Thanks for your questions. I will try to answere them 😉

1)

7 hours ago, Frank Vèssia said:

I can't find the submit button texts inside translation files

The translations should be still there... maybe you have not installed the files of this module???

The translations for the button texts are inside each template file for each page of the module. Take a look here:

The files are for example for the DeleteAccountPage.php, DeleteRequestPage.php and so on. This files include the texts for the submit buttons.

If these translation files are not present inside your installation, then you have not installed it. To install it, please click on the "Find files to translate" button and select all files of this module. Afterwards the translation files must be visible inside the language files.

2)

7 hours ago, Frank Vèssia said:

Is there a way to choose the position of the privacy check inside the form? right now it appears on top of everything when usually is at the end. Also I have an external privacy policy but in settings I can only choose an internal page.

This should not happen. I will check this if no Captcha is enabled. Link to an external page is a good idea for a feature request. I will add this feature to the module in the future. 🙂 At the moment it is not possible.

3)

7 hours ago, Frank Vèssia said:

I have few input fields text inside my user template (name, surname, age, ecc..) but they don't show up on the settings select

Only fields that can be edited by the user will be displayed in the select. If you do not have enabled it inside the user template, the custom user fields will not be displayed. So please check if you have toggled the checkbox next to the field inside the user template. In this example I have added the field "Age", which is an integer field.

As you can see the custom field age is checked and now it can be selected inside the select too.

 

4)

7 hours ago, Frank Vèssia said:

Since my website is also an app for Android and iOs, the app stores ask for a public account deletion link but your system is a private page for the already logged in user. In my other websites I have a form where user can put the email and if the email exists it sends a confirmation via email.

You can make the page public by changing the visibility inside the template for the deletion link. The templates name is "fl_deleterequestpage". So please go to "templates" select the template with the name ""fl_deleterequestpage" and change the access level to public by checking "guest" instead of "registered".

Hope this helps!!

[Frank Vèssia]

Thanks for the fast reply. Yes some translation files were not installed, I didn't check properly, sorry.
 

2 hours ago, Juergen said:

You can make the page public by changing the visibility inside the template for the deletion link. The templates name is "fl_deleterequestpage". So please go to "templates" select the template with the name ""fl_deleterequestpage" and change the access level to public by checking "guest" instead of "registered".

Mhhm, I already tried that but that page assumes the user is already logged in and ask only for the password for confirmation, there is no way request a deletion for not logged in user. I will try something else, don't worry, it's not a big deal.

Regarding custom fields, I checked my text fields but I get a fatal error because they are multilanguage text fields, if I change them to normal text fields it works.

Fatal Error: Uncaught TypeError: FrontendForms\Form::add(): Argument #1 ($field) must be of type FrontendForms\Markup|FrontendForms\Inputfields|FrontendForms\Textelements|FrontendForms\Button|FrontendForms\FieldsetOpen|FrontendForms\FieldsetClose, null given, called in /site/modules/FrontendLoginRegister/pages/FrontendLoginRegisterPages.php on line 858 and defined in /site/modules/FrontendForms/Formelements/Form.php:3177 Stack trace:

 

[Juergen]

4 minutes ago, Frank Vèssia said:

Mhhm, I already tried that but that page assumes the user is already logged in and ask only for the password for confirmation, there is no way request a deletion for not logged in user. I will try something else, don't worry, it's not a big deal.

Ok, I see - There is an additional check if user is guest inside the DeleteRequestPage.php on line 35

// if user is guest -> not allowed to be here -> let's redirect to the homepage
            $this->redirectToHomepage(true);

If you comment this out, it should work. I will add a new setting in the backend config, where you can choose if the page should be public reachable or not. For now, commenting out this code line should help you.

[Juergen]

36 minutes ago, Frank Vèssia said:

Regarding custom fields, I checked my text fields but I get a fatal error because they are multilanguage text fields, if I change them to normal text fields it works.

I will take a closer look on the weekend.

[Andy]

18 hours ago, Juergen said:

This should not happen. I will check this if no Captcha is enabled. Link to an external page is a good idea for a feature request. I will add this feature to the module in the future. 🙂 At the moment it is not possible.

I think it is possible even now. You can add a “I agree with the personal data policy” field to the customer profile. And make a link to the policies outside the form. 

[Frank Vèssia]

1 minute ago, Andy said:

I think it is possible even now. You can add a “I agree with the personal data policy” field to the customer profile. And make a link to the policies outside the form. 

It's no compliant...better solution: link an internal blank page which redirects to the external url policy 😉

[Juergen]

I will add an additional configuration field in the backend, where you can select if you want to use an internal page or enter the link to an external page for linking to the privacy page.

[Juergen]

The following issues should be solved now:

• The position of the privacy check is now always at the bottom, regardless of the use of a CAPTCHA (bug fixed)

• New configuration field to select whether to use an internal or external page for the privacy policy added. This configuration supports multilingualism, which means you can select a different page for each language.

These issues have been fixed in the FrontenForms module and not in the FrontendLoginRegister module. This means that you will need to update the FrontendForms module to the latest version 2.2.27 to fix these issues.

The other problems (public deletion link, multilanguage user fields) directly affect the FrontendLoginRegister module and must be solved there. I will try to solve these issues in the next time.

You can read the full documentation of changes in the changelog.md.

Hope it works now as expected without problems!!

[Juergen]

FrontendLoginRegister module is updated now (Version 1.3.6)

The following last 2 issues have been fixed now:

• Support for usage of multilanguage fields inside user template added
• New configuration field to make the "Request deletion of user account page" public viewable added

Screenshot of the new configuration field to change the access of the user account deletion page:

In the middle you can see the "Allow public deletion of a user account" checkbox. If you check this checkbox, the deletion page will be public reachable.

For more information check the changelog.md.

Please keep in mind! This module is Beta stage, so it is not recommended to update live sites without testing it locally before! I have tested various scenarious, but I cannot test all possible cases - so happy testing 😉

As always, please report any issues here or on GitHub.

 

[Frank Vèssia]

Thanks for the additions, great work!