Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#391 2017-05-18 07:39:45
- Dragondz
- Moderator
- From: Algérie
- Registered: 2005-06-12
- Posts: 1,303
- Website
Re: mem_self_register
Hi Yianis
Yes i can replicate it! very strange! the change is that instead of using mem_form_email i used mem_form_hidden but i enforced it by using required=“1”, but even with that i see that an sql statement like that works on DB :
INSERT INTO `txp_users` (name,pass,RealName,email,privs) VALUES('test','test','Test','','5')Offline
#392 2017-05-18 10:53:38
- Bloke
- Developer
- From: Leeds, UK
- Registered: 2006-01-29
- Posts: 8,607
- Website
Re: mem_self_register
Dragondz wrote #305727:
i see that an sql statement like that works on DB :INSERT INTO `txp_users` (name,pass,RealName,email,privs) VALUES
We’ve never enforced email address in core, as far as I’m aware. It can’t be NULL, but defaults to '' (empty string) if none is supplied. So if mem_self_reg isn’t passing one in, core won’t trap it. It’s up to the plugin or your business logic to enforce it.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
#393 2017-05-20 08:57:46
- Dragondz
- Moderator
- From: Algérie
- Registered: 2005-06-12
- Posts: 1,303
- Website
Re: mem_self_register
Thanks for clarification Stef.
The problem happen because i use mem_form_hidden that i think is not checking required attribute, if i use mem_form_email it checks if there is a valid email inserted.
Cheers.
Offline