CB Conditional

I have created a field (Drop Down Single Select) called cb_usertype..

And for a certain tabs, I applied the condition plugin, if the field cb_usertype

equal to

value: admin (translation: enable)

then mode = hide

For

Registration: Disabled
Profile Edit: Enabled
Profile View: Enabled

As

Direction: 2 way

---

The problem is when the moderator tries updates a user profile with the field cb_usertype (which I mentioned earlier) is empty, I get a notification that Apache has stopped working.

Tried Direction as 1 way but the problem still persist.

It is okay if the update is done through Ajax field update.

I think I found the problem. The tab which the field (cb_usertype) is located, cannot impose a condition if the field is under that particular tab.

The moment, I remove the condition on the tab, everything is back to normal.

Try not to have fields condition them selves or tabs conditioned by a field on it self. This causes odd conflicts as the condition will see the field isn't accessible and will remove it as well as stop the new value from saving so basically the field won't save.

@krileon,

I believe I'm currently having this issue. I have a conditional field (field conditional to others) for another field in the same "contact us" tab. My conditional field is acting strangely and doesn't save/work 90% of the time. I will select which fields to show and they don't show on some of my conditions (I have 4 instances in one) but show in others? I can change the "show" but it doesn't save.

It's almost like the database is confused? I know this explanation isn't as clear as I would like it to be but again I'm not sure why it's acting so strangely.

After a lot of testing I think it's only allowing me to have one condition per field. Right now I have four member types based on the member type one selects they get another drop-down showing the specific status. The conditions for only one of the four member types will work at one time.

Don't condition the same field multiple times. If you do this then only the last condition triggered will apply. You need to reconsider your conditional configuration to avoid conflicts. For example if you have a profile type field and it's supposed to show/hide various fields then don't place the condition on the profile type field. Instead place it on the fields that are supposed to be specific to a profile type. If you need to match multiple profile types while doing this you can use the REGEX operator to match multiple types using REGEX (e.g. /Type1|Type2|Type3/).