[SOLVED] bug in conditional 4.x plugin

OK, installed 4.0.2 but still no success.

I have the exact same setup as on CB 1.9. Why did you change that behaviour? I have to readjust EVERYTHING. This is not a 2.0 updadte, this a virgin install process.

On my CB 1.9 reg form only that select field was displayed on page load. It worked as intended. All other fields were hidden because the "Empty" option was applied correctly (in hiding all fields but the select itself).

Now all the fields are displayed on page load ... what a frustration, so much work for things that were done already ...

Please PM backend super administrator login credentials as well as include what field is giving you problems and will take a look.

CB 2.0 is a migration. You just don't see the migration as we do it during install. It's equal to going from Joomla 1.5 to Joomla 3.3. It's not a small change.

Only the last conditional on a field is relevant. If you condition a field 5 times then the 5th condition is the only condition that matters. This is because it's not a matter of AND/OR. The conditions are completely independent of one another. AND/OR support is planned in a later release.

"Only the last conditional on a field is relevant."

Ok?!

1. Why are there 5 tabs = 5 conditions?
2. How do I condition the different values if only one tab gets recognised?

Why are there 5 tabs = 5 conditions?

Because people kept asking for it and a single field can conditional multiple separate fields by doing this. The issue is when you tell a field to show/hide 5 different times that it's going to cause problems. As in such a situation it doesn't know what to do. Should it keep the first condition? The last condition? Combine the conditions into an AND statement? Combing them with an AND operator would be the ideal situation, but that's not implemented yet.

How do I condition the different values if only one tab gets recognised?

I've no idea what kind of scenario you're trying to implement so I've no idea what to suggest. Are you hiding every field then having those individual fields condition again based off something else? That's a situation I could this is problem happening. If that is the case do the other conditions on those fields function?

In CB19 I had no problem getting the desired result because it was quite obvious how the conditioning works. But now I have no clue what this thing does.

My goal:
- two options in the select drop down: o1 and o2
- a number of fields are conditioned by that select field
- condition 1: on page load the default option is the "empty" option hence only the select field is displayed
- condition 2: user selects o1 and the specified fields are displayed/hidden
- condition 3: user selects o2 and the specified fields are displayed/hidden

This was easy in CB19 and seems to be impossible in CB20.

Try disabling condition 1 as it does not sound like it's needed. If condition 2 shows/hides a set of inputs then condition 3 shows/hides a set of inputs then condition 1 is pointless double conditioning.

A lot of this behavior was bugged in older releases of CB Conditionals. The jQuery was not reliable. The jQuery plugin I've completely rewritten to give reliable results and it's setup in preparation for AND/OR implementation. As it stands since AND/OR is not implemented it only cares about the final conditional.

Please PM backend super administrator login credentials so I can better review your conditional usage and duplicate locally. In doing so I'll be able to see better what behavior is going on for your usage.