[SOLVED] Registration form can not be sent even registration is allowed in CB settings

Hi,
ok so i did now the update to 3.07. but this seems to change the logic of my coditions as well as now it is impossible to reach the last process stept - captcha within a defined condition.

so i changed to another condition wich only displays a limited set of fields and tried to register but still the register button does not work.
in error console i get this:


Zeitstempel: 03.05.13 19:19:27
Fehler: ReferenceError: PostAffTracker is not defined
Quelldatei: aita.iq310.com/component/comprofiler/registers
Zeile: 349


there are also several warnings like this

Zeitstempel: 03.05.13 19:19:27
Warnung: Fehler beim Verarbeiten des Wertes für 'height'. Deklaration ignoriert.
Quelldatei: aita.iq310.com/component/comprofiler/registers
Zeile: 0

Zeitstempel: 03.05.13 19:30:20
Warnung: ReferenceError: deprecated arguments usage
Quelldatei: aita.iq310.com/components/com_comprofiler/js/overlib_all_mini.js?v=74886f53156cae88
Zeile: 30

ok so it seems to be a problem with the condition plugin from my understanding
what can i do now to get my condition back working and more to get the register process to work again

ok so i did now the update to 3.07. but this seems to change the logic of my coditions as well as now it is impossible to reach the last process stept - captcha within a defined condition.

A couple of logic bugs were fixed with latest release. There was some tab hiding conditional issues that needed fixed. So the usage you experienced before was actually a bug.

Reviewed source on your page and you have several Date of Birth fields that are marked as required. You probably have a double conditional issue. Please review those fields conditionals and adjust as needed. You're setting them required or not-required at the same time as disabling their tabs and causing their conditions to conflict. This results in hidden required fields, which will cause jQuery form validation to fail.

Ok as well i checked now what happens after disabling the tabbed condition and this does not work as well. same error feedback as before.

ok so from my understanding i have to set them to "not required " so they will not conflict after a tab is hidden. did i get that right or may i set them without any condition to "required" and if the tab is hidden because of a other condition they will not throw an error message because of a mandantory state?

Ok as well i checked now what happens after disabling the tabbed condition and this does not work as well. same error feedback as before.

Don't understand the issue, tab conditionals seam to be working fine to me. You have a lot going on, it's extremely easy to create conflicting conditionals. Multiple conditions on a tab or field run independent from one another.

ok so from my understanding i have to set them to "not required " so they will not conflict after a tab is hidden. did i get that right or may i set them without any condition to "required" and if the tab is hidden because of a other condition they will not throw an error message because of a mandantory state?

Are you setting the field as required or not required using a conditional or is it already set to required with no conditional?

Aha, was able to duplicate the field required bug. Will review fixing for next release. It happens when a field is set to Required after the tab has already been hidden and the field was originally set as Required. When setting the Required state of a field it should make sure the tab isn't hidden first.