We set about 20 fields to be dependent on one field by "conditional self". Don't know how else to outline the complex situation. I can send you login to the site in PM and you have a look to get the info you need?

The memory issue is new, but thanks for advice on this!

That's what I had done; set many fields to "Conditional self" based upon the actions of one field. Example: If a checkbox called "cb_checkbox" is Not Empty (checked) then I had set every field to conditional self. I don't know how many fields were set like that (I'm guessing maybe 25) and that's when the crashes began. (Sorry Kyle, I don't have any other specifics)

I fixed the problem when I went to the cb_checkbox field and used "conditional others" to manipulate the fields to my specs.

It seems that "Many to one" (the first method outlined) causes problems and it's better practice to use "one to many" (as per the second instructions).

As the form further developed I ended up using the conditional self on a few fields without problem.

Today I learned about CB Conditional... (TL;DR)

• Use a "One to many" approach when creating large amounts of show/hides.
• Use the conditional self for small nips and tucks.
• In the backend of the CB Conditional plugin there's a "Tools" option. That can help you solve problems.

Very plausible with the "one to many" guideline as it also makes configuration quicker.

Unfortunately a one to many with cond. others of a single select dropdown with 2 options did not quite work out - therefore we chose cond. self of about 20 fields (mostly single or multiple option dropdowns).

Will go through them now as krileon suggested and get back asap.

Isolated TEXTAREA fieldtype causing the error.