form validation over multiple fields

getting closer

with [value] I get better, but not yet perfect solutions.

This code gives me only results, that are evaluated with "true" (even when the fields sum up to 0).

that's why I'm not sure whether the fields are evaluated against each other as they should.

I also tried to return the result as false and as true (with an if - else -statement). But it did't work as supposed.

I really need your help for this tricky question - thank's a lot in advanced

The code provided will evaluate to true or false as is intended. Validation code must return true for valid and false for invalid. It currently will evaluate to true as long as 1 of the 2 fields is greater than 0. If that's not what you were wanting then I don't understand what you're wanting it to validate against. If you want to validate against the sum of the 2 fields you'd need to use the below code with [value] replacing [cb_field1] or [cb_field2] where needed.

Sorry, me again.
Everything you say is logical and as a php programmer I understand the code quiet well.
What I don't understand is the behaving of my form on the frontend.
As you can get a better insight in my problem I made a short screen-movie.
Please have a look at it under this www.dropbox.com/s/wu7lobewybj19mn/Code%20validation.mp4?dl=0URL .

You'r my last hope - if you can't give me an indication what could be wrong - I will try to reach my goal with a work-around.

Sorry, but CB behaves really a little bit strange at this point - as far as I see.

thanks for your help

The validation on cb_garten2 is incorrect. In its validation you need to replace [cb_garten2] with [value]. Anytime you're trying to use the fields own value in the validation you need to use [value]. Its validation should be as follows.


The validation on cb_haus2 should be as follows.


That should work and does in my tests, but there's a caching bug that's causing existing values to validate a little oddly. Have added a bug ticket to fix the caching issue.

forge.joomlapolis.com/issues/7795

Ok, the caching issue has now been fixed in latest CB Code Field and CB Query Field validation integrations. The above exact usecase appears fully functional in my tests. Please update to latest builds releases as of now using the above usecase code.

perfect - now it works fine

sometimes it takes two times to save new values, but it works

It is not possible to change directly
from field1 = 1 and field2 = 0
to field 1 = 0 and field2 = 1

But I think we and our members will come clear with this.

Thank you for you help and your endurance