FEU3 and cgfr_username_whitelist if username is not email

[raiyul]

I am testing FEU3. I see that the white list is only active when username is email. This restriction were active in the older versions (FEU version < 2.99). Why not change this by a next update of CGFEURegister? I don't see why it would not be possible! I don't see why I should update from FEU v2.12.6 when I cannot define a white list when username and email are separated. It would be so fine if possible to extend that white list to the explained situation. It seems, there is a similar problem by on_register. But I should make more tests.

[raiyul]

Perhaps a solution for the white list would be to have a list with name 'cgfr_useremail_whitelist' for the case where user-name and email are not same and the already defined cgfr_username_whitelist for the case where user-name is email. And a similar double definition for the black list.
The problem of sending an email to verify the email is also to be solved when user-name is not user-email.

[raiyul]

Before I wrote this reply, I could test with success a case with an email as user (but no white list) and config set for such a case.
Here a small explanation what happens (rather doesn’t happen) if user is not email, config set for such a case and some user want to register.

• - The post_register_message.tpl doesn’t appear on the page;
• - the on_register.eml email is not sent;
• - but no error message or warning is sent!!! That means all is correct on user-side.

This is to be corrected and the activation of a white list should be added for this case where user name is not email.
I am certainly not alone with these problems. I am still waiting on corrections and extension.

[raiyul]

FrontendUsers::PROPTYPE_EMAIL

Searching how CGFEURegister is working I would be glad to find an explanation concerning
the function FrontendUsers::PROPTYPE_EMAIL and to know where it is defined

[raiyul]

I am testing FEU3. I see that the white list is only active when username is email. This restriction were active in the older versions (FEU version < 2.99). Why not change this by a next update of CGFEURegister? I don't see why it would not be possible! I don't see why I should update from FEU v2.12.6 when I cannot define a white list when username and email are separated. It would be so fine if possible to extend that white list to the explained situation. It seems, there is a similar problem by on_register. But I should make more tests.

False, the white_list doesn't react. It is as there were none.