eMember – Form Builder Addon Registration Forms

[MapleLion]

My site requires two different registration pages. A registration page for members and a registration page for instructors. I was lead to believe the form builder addon was capable of this function. I have created the respective pages. I have created the forms in the form builder. I have tried a million different shortcode combinations to get the appropriate form to display on the appropriate page, yet to no avail. It still only displays the generic one, whose fields are only affected by the custom fields in the eMember custom fields settings. What am I doing wrong?

This needs to be up by next week, so any help is greatly appreciated.

[admin]

First, please read the following post to understand how the registration system works in eMember:

https://support.tipsandtricks-hq.com/forums/topic/how-one-single-registration-form-is-used-in-emember-for-all-types-of-membership

Next, I am guessing you want to create different registration pages (with different forms that you built using form builder addon). Please take a look at the following documentation:

http://www.tipsandtricks-hq.com/wordpress-membership/create-a-registration-form-for-a-particular-membership-level-429

Is that what you want to do? Do you have a page where you used that particular registration form shortcode?

[clearscopedesign]

We use 4 custom fields in our registration forms. For brevity’s sake we will call them: Field A, Field B, Field C and Field D.

Because we need to have some registration forms that do not include these custom fields, you directed us to purchase the Form Builder Addon.

However, we are having trouble understanding the best way to manage this and we really do not understand why the custom fields cannot be global within the account.

As you explained via email, “The form builder is a completely separate addon. It doesn’t have any relationship with the custom fields that you can configure in the custom fields menu of the plugin.”

So this means that we have to create duplicate versions of Field A, Field B, Field C and Field D, and the original versions of Field A, Field B, Field C and Field D that already exist within eMember become obsolete (even though data still exists within them).

However, additionally, it seems that each registration form that we create with the Form Builder Addon that needs to include Field A, Field B, Field C and Field D then creates another new version of Field A, Field B, Field C and Field D.

If we have 4 different registration forms (for 4 different membership levels), that each contain Field A, Field B, Field C and Field D, that then makes 4 different versions of each of those fields (plus the original version of these 4 fields that already exist within eMember).

This equals 5 versions of the same 4 fields. This means there are 20 custom fields total appearing under each account, when all we need is the 4 custom fields.

Is this really the intended behavior? It is very confusing and convoluted to keep track of.

[zora_db]

I would like an answer to clearscopedesign’s question above, as I need 6 different registration forms with customs fields that do overlap between registration types. I need all the data to be in the same place.

[admin]

I am not really sure what you mean by having to keep track of these fields.

A member belongs to a membership level. When you edit a member profile, you will see the fields according to his membership level.

If you want to edit the fields of a membership level then you edit the level and you will only see fields configured for that level.

[clearscopedesign]

We are following up with this again now because we have a new membership level whose registration form we do not want to include some of our standard custom fields.

Previously you directed us to use the eMember Form Builder add-on plugin for this purpose. However, we never ended up using the eMember Form Builder add-on plugin at that time because of the duplicate fields issue mentioned above.

We were able to get by before by just letting all custom fields appear in all registration forms, as happens by default. But now, with this new membership level, it is really a necessity that we be able to exclude some of the custom fields from this registration form.

Can you please tell us:

1) Is there any way that standard custom fields can be excluded from certain membership level registration forms without using the eMember Form Builder add-on plugin?

2) Or, is there any way that the custom fields created with the eMember Form Builder add-on plugin can be made global (so that they are not created anew / duplicated for each membership level that uses them)? If a fix for this does not already exist, could it be achieved through some custom paid development?

Also, to clarify for you the issue that zora_db was reporting:

This is the same exact issue that we reported previously. That is, when multiple membership levels need to use the same custom fields, the eMember Form Builder add-on plugin forces those fields to be created anew in each case, essentially creating separate new / duplicate versions of the same custom fields for each level that uses them.

When she said, “I need 6 different registration forms with customs fields that do overlap between registration types. I need all the data to be in the same place.” This is the exact same issue that we already reported. That is, to have multiple registration forms, some of which contain some of the same custom fields, without those custom fields actually being separate fields in the database as eMember Form Builder seems to do. Rather, we need those custom fields to actually BE the same field within the database, not new duplicate separate versions of the same field. This seems like it should be pretty straightforward, and we don’t quite understand why anyone would want the duplicate behavior that currently exists (if there is a need for a separate field than you can just create a separate field; if you are using the same field, presumably you want that to be the same field).

If this functionality is not currently available with the current setup, can it be achieved through some custom development? The existing functionality of not being able to specify which custom fields appear in a given registration form is very limited and it is really a necessity for us that this be fixed.

Thank you!

[Author]

Posts