Issue with Field Conditionals Not Working

You would need to uninstall GJ 2.x and delete the _groupjive database tables then install GJ 3.x. It has no migration code yet so it can not migrate from GJ 2.x at this time. As it's a Beta I don't recommend using it in a live environment.

Thanks. I'll do what I can to not use GJ at all for now.

But, I'm still having issues with the field conditionals. I'm convinced it's a bug, but who knows. Last time, it wasn't 'turned on'.

The first conditional I have set is:

Display:field conditional others
Operator:empty
Fields>Hide: I selected all except for the field that has the conditional

There are company and individual fields...

2nd conditional:

Operator>equal to: Individual
show individual fields & hide company fields

3rd conditional:

Operator>equal to: Company
show company fields & hide individual fields

When you load the page, all the company fields are displaying even though the first conditional says to show none if empty.

I've tried switching the field type between radio button and single select. And I've tried switching the operator from 'equal to' to 'does contain'... still won't work.

URL of registration is 8130-3.tjohns.co/cb-registration

Now, even the 'empty' operator isn't working. I'm pretty sure that the 'field conditional others' just doesn't work.

Another note... now it just seems to be showing some individual fields & some company fields.. seems like it is just showing random fields.

You can not condition the same field multiple times. If you've 3 different conditions showing/hiding Field A then only the last condition applied to it matters. Empty operator is pretty strict and only really functions with fields like text, textarea, or a dropdown select that isn't marked required (will have an empty option).

Thanks, Kyle. I think the best way to go about it is to use 'field conditional self' on all the fields I want effected. I'll have to set it on 14 fields instead of just one, but 99% sure that worked on a previous project if I remember right.

Yup, field conditional self is the best way to go. In fact in a later release conditional others will likely be removed as it's just too unreliable and prone to cause multi-condition issues. AND/OR conditional usage is also planned at some point to allow multi-condition usages.