[SOLVED] Use a password to register

Thanks but I'm still struggling with creating the query, the two fields I am trying to compare are text fields, is this the start of my problems? should these be password fields?

First I have the groupjive user group selected from a cbgjautojoin field on the registration form, I need to locate the owner of the selected group.

Once I have the group owner I need to get a text field from their profile.

Then confirm that this is the same as a text field entered on the registration form by the new user. I can see Field entry validation in the field but can't see how I would link this to the query field.

Regards,
Andrew

It doesn't particularly matter what type of field it is. Below example should work fine.

Text Field 1 (cb_text1): This is for the first user to supply a password to match against.

Text Field 2 (cb_text2): This is for the new user to supply a password to match against the first user. See the below Query Validation usage to validate it.

Query: Validate On: Successful Results

That should cause the Text Field 2 to only validate if the value supplied matches a users Text Field 1 value.

Excellent, that works, but the same password works with all groups.

As there are multiple groups, each with their own password when created how do I get the password for the selected group into the query?

The user selects the group to join from a cbgjautojoin field on the registration form, and the owner of the group has the password in their profile.

Regards,
Andrew

You can't. The ajax doesn't know the other fields values. It can only know the value of the field being edited.

OK, I will need to rethink this then.

Is it possible to create an auto action to verify the fields and approve or reject the registration?

Regards,
Andrew

No, CB Auto Actions is designed to not interrupt a triggers normal behavior. Registration also ignores user cancel so redirecting won't stop registration. It maybe possible to set a $_PLUGIN global error in a Code action with PHP method, but I'm not sure if that'll stop it or not. Ideally you should create a new fieldtype plugin that fits your specific needs; I can't really see a way to generalize what you're wanting.