CMS Made Simple Forums

There are errors in white and black lists in CGFEURegister. If I go to the Bug Tracker, I see a description of these errors and how to correct them. But till now I didn’t see an updated version CGFEURegister. It's still version 1.04. Can somebody of the Forge correct these errors? Normally it's assi...

Many thanks

I could put the code changes by The Forge

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.1...

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

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_me...

I notice solved because I know where the error lies: sending an email to verify the email when user-name is not user-email is not running well. I wait until it is solved. There is a new post about this error and the whitelist for the case user-name is not email.

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 proble...

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...

Many thanks, but a problem lies in the first step. You write : Assuming a default installation where you are calling {CGFEURegister group='somegroup'} on your 'Frontend User Registration' page. And the user must verify his email address. Then, once the user registers an email must be sent to the use...

For the first message, no addresses , I found a convenient solution for my case, I put in the config.php file a $config['cgfr_username_whitelist'] entry with authorized email addresses. But the user is still finishing in the page Frontend User Registrations . Could emails/on_register.eml solve the ...

I try to use FEU version 3. The biggest problem I have is to use correctly CGFEURegister. Only writing on my page {CGFEURegister group='potentiel'} give me an error: "Cannot send email... no addresses" . And the new registered user is in the page Frontend User Registrations . I try to unde...

I had the same problem and I discovered today morning and dating from yesterday a version 1.11.1 of SelfRegistration. With the update of the module, the problem by me is solved.
Thanks !

With whitespace around all of your comparison operators it's OK.
Many thanks for the answer

On a page I had this code : {if feu_smarty::is_user_memberof('Auteurs,Membres,potentiel')} I choose this page page {Navigator template="nautres.tpl"} {else} You must be member {/if} and the content of template nautres.tpl was {if !isset($depth)}{$depth=0}{/if} {if isset($nodes)}{strip} <ul...