Thread

They worked fine in 2.1.1 but on 2.1.3 when I click register it just says they are required and won’t let me create the new users.

Any help please?

I don’t follow exactly. What fields are required? Can you show us some code, or better yet a link to your site?

I created two custom fields using the ACP called ‘First Name’ and ‘Last Name’

I set both fields to be required when user submits either stand alone entry form or if they use the registration form built into the members module. When I fill out the form along with the two new custom fields, it establishes that they are required fields, but even though I have field them our with values, it seems to think they are null.

There is no coding or anything on my part besides creating a simple html form, so effectively this is built into the functionality of EE and the members module surely.

MjMAC87,

Can you confirm what you mean by ‘ACP’

I set both fields to be required when user submits either stand alone entry form or if they use the registration form built into the members module.

I am not sure how your SAEF would come into play here. The SAEF is for adding entries and has nothing to do with member registration.

Can you take a screenshot of your member registration page please?

When you updated your version from 2.1.1 to 2.1.3 did you follow the version update docs or the build update docs?
Did you update you themes folder?

I have tested this and can’t replicate what is happening to yourself.

Sorry for the long delay in replying.

ACP = Admin Control Panel

I am not sure, but when I first started to grips with EE, when trying to create a custom registration/login form, I found that threads on the net referred to forms on the user end as stand alone entry forms.

Basically I have a custom registration form, which uses the action id that relates to that which is connected to the registration action.

I never did upgrade from 2.1.1 to 2.1.3. I use EE at work and the version was 2.1.1 when I installed it at work whereas at home 2.1.3 had been released. I followed the same steps to produce the custom member fields.

On top of this, it has now happened to my EE version at work. So I am assuming there is something conflicting (possibly an add-on) with the members module. I am struggling to pinpoint it.

Oh and If the fields are set to ‘Not required’ nothing gets inserted into the database.

Hi, MjMAC87.

Is there a particular reason you are doing your own registration instead of what’s built into EE?

yeah, so I can customise it. I want a custom front end for users to register/login etc.

Anyway, I spent a few hours last night trying to back trace the problem, to find it wasn’t actually a problem at all. I am certain that I had the form working using the custom field names (not the labels) but upon looking at the php within the members module for the registration action, I found that the input names had to be m_field_id_xxx where xxx represents the ID of the field.

I did get it all working, but I would like to suggest the ability for the members module to utilize the custom member fields name rather that it’s id, would make it a hell of a lot easier.

I would make the changes to the module myself, but if you end up updating the members module your end, it would make updating it my end a lot more difficult lol

I want a custom front end for users to register/login etc.

Wouldn’t it still be easier to let EE do the heavy lifting, as it were, and just style the member templates accordingly?

I did get it all working, but I would like to suggest the ability for the members module to utilize the custom member fields name rather that it’s id, would make it a hell of a lot easier.

Thank you for your feedback. Perhaps you’d want to make it an official Feature Request, so to speak?