[#6093] CB Conditional 3 or more fields

I upgraded to the latest version Conditional CB (plug_cbconditional_4.0.7+build.2016.07.06.03.13.58.c8e1354cc).
I noticed that the reset of the database fields reported in this link forge.joomlapolis.com/issues/6084 seems to work after saving the profile while should act before saving your profile such as may act CB AutoAction onBeforeUserProfileSaveRequest. Although now it clears the fields for me still remains the problem of signaling required fields that instead the problem disappears if I act CB AutoAction onBeforeUserProfileSaveRequest
Thank you

No, it's working exactly as intended. It will reset via the jQuery and on save only.

A field erroring that it is required when it has been hidden has nothing to do with the reset functionality and is likely the result of a double condition. You can not condition the same field twice. The conditions will conflict. In PHP likely what is happening is the second condition is toggling the field displayed again resulting in the required condition triggering. Please review your conditions carefully.

I will not insist, but I would advise you to try to create the scenario I mentioned www.joomlapolis.com/forum/153-professional-member-support/234100-cb-conditional-3-or-more-fields?limitstart=0#283391

Set three all required fields. CampoB conditioned to CampoA and CampoC conditioned to CampoB.

First time you save all three fields are filled, and works well. Then try changing profile while CB Conditional displays only the first (Field A), the view is correct but can not be saved because it produces error of field B and C because it required but are not visible. After upgrading the latest version of CB Conditional it changed that if I try to still be saved the error disappears and the profile is updated properly.
This may be the reason my idea that he needs to try to save to reset the fields.

I have configured your usage. Our demosite has a 4 field chain to demo CB Conditional. I've made 2-4 marked required. It works perfectly fine. You can try this you self as well if you like by visiting our demosite below, filter field management to CB Conditional tab, then mark fields 2-4 using the batch tools as required then on frontend try it out. Next demosite refresh will have latest CB Conditional and the conditioned fields marked required by default (it is also working fine on our reference site).

You have a condition conflict or you've something else affecting how fields load.

On your demo site is exactly the same mistake that I reported.
It requires you to fill out required field (hidden by CB Conditional) if it is not visible.

I have no idea how you're possibly triggering that. It is working perfectly fine here. My CB Conditional configuration changes have been updated to the demosite where they're marked required and is working fine.

Please describe your exact steps step by step to cause your issue on the demosite.