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

ok even after removing the regex i get the error 42.

ok now it seems that the error 42 is one thing that has to do with a not correct handling of a database delete of users and so it is a sidetree. (i removed my demo user several times to test but it is only removed in the frontend interface via the CB user manager feature )

the main problem with the conditions is now the folloowing - i have set up the process so it is possible to register. but if the registration form is shown with several tabs for additional users (like i described by adding a number in the filed under the radio button group) only the first additional user ist saved and will show up later on in the backend user manager. from the second additional user (tab p2) on data are not saved. ;-(
i have no idea if this is due to the fix you provided ?
any idea how to get this thing working ?

as the page is now set life i have additionaly the problem to keep both databases and filerepositorys in sync so it would be great if you could provide me a downloadable fix so i can apply it to the life site as well?

thanks!
Carsten

the main problem with the conditions is now the folloowing - i have set up the process so it is possible to register. but if the registration form is shown with several tabs for additional users (like i described by adding a number in the filed under the radio button group) only the first additional user ist saved and will show up later on in the backend user manager. from the second additional user (tab p2) on data are not saved. ;-(
i have no idea if this is due to the fix you provided ?
any idea how to get this thing working ?

I have a good idea what could be doing this. You have your numbered tabs being conditioned by 2 different fields. 1 of the conditions is passing and the other is not. This causes the tab to be shown then the tab to be hidden in PHP. When the tab is hidden and value resetting is enabled it'll reset all the values on the hidden tab. So PHP is seeing the field shown then hidden due to double conditionals.

This is basically working as intended as described early you should not double condition tabs/fields as it can cause issues due to the conditions fighting for control. Always keep in mind that multiple conditions on a tab/field act independent of one another (it is not an AND or OR case). For example instead of having 2 fields control the number of tabs, renamed 1 of them, and remove the other; make it general. This way only 1 field is controlling the tabs and you completely eliminate this issue.

as the page is now set life i have additionaly the problem to keep both databases and filerepositorys in sync so it would be great if you could provide me a downloadable fix so i can apply it to the life site as well?

I should have a release out either today or tomorrow as still need to fix step skipping in step by step.

krileon wrote:

the main problem with the conditions is now the folloowing - i have set up the process so it is possible to register. but if the registration form is shown with several tabs for additional users (like i described by adding a number in the filed under the radio button group) only the first additional user ist saved and will show up later on in the backend user manager. from the second additional user (tab p2) on data are not saved. ;-(
i have no idea if this is due to the fix you provided ?
any idea how to get this thing working ?

I have a good idea what could be doing this. You have your numbered tabs being conditioned by 2 different fields. 1 of the conditions is passing and the other is not. This causes the tab to be shown then the tab to be hidden in PHP. When the tab is hidden and value resetting is enabled it'll reset all the values on the hidden tab. So PHP is seeing the field shown then hidden due to double conditionals.

This is basically working as intended as described early you should not double condition tabs/fields as it can cause issues due to the conditions fighting for control. Always keep in mind that multiple conditions on a tab/field act independent of one another (it is not an AND or OR case). For example instead of having 2 fields control the number of tabs, renamed 1 of them, and remove the other; make it general. This way only 1 field is controlling the tabs and you completely eliminate this issue.

Hm ok this might be a explanation. but is there a way to dynamicly change the lable of a field as i have to deal with different wordings to be sure the users understand what thy have to fill in. eg the field might be labeld "ibput red" "input green" so there is no inbetween like put in red or green as many people will put in the wrong color. so a dynamic label would be another solution for that but i have no idea how to get this done in CB.

as the page is now set life i have additionaly the problem to keep both databases and filerepositorys in sync so it would be great if you could provide me a downloadable fix so i can apply it to the life site as well? I should have a release out either today or tomorrow as still need to fix step skipping in step by step.

Ok this will be 3.08 ? just to know what to look for...

Hm ok this might be a explanation. but is there a way to dynamicly change the lable of a field as i have to deal with different wordings to be sure the users understand what thy have to fill in. eg the field might be labeld "ibput red" "input green" so there is no inbetween like put in red or green as many people will put in the wrong color. so a dynamic label would be another solution for that but i have no idea how to get this done in CB.

No, I suggest using as generic as possible field titles. You can use multiple conditionals, but you need to be careful how they're setup as if 1 conditional matches, but the other doesn't then you have 1 showing the tab/field and 1 hiding the tab/field. Hiding always happens last so if it gets hidden once it'll be removed.

I need to think about if I want to change this behavior or not, but the concern is changing it now risks breaking a lot of current usages. Maybe a parameter to enable in backend so only the last conditional applied will work for a tab/field. Even if I implemented this then it'd just be the reverse issue. For example if the First conditional Shows the tab and the second conditional Hides the tab it'd just keep flip flopping. What you may need to use is One-Way conditionals. These are conditionals that won't do their opposite if not matched. For example if I show a field based off another fields value and it's One-Way then it won't hide if the value is wrong.

Ok this will be 3.08 ? just to know what to look for...

Yup, 3.0.8 is released as of yesterday.

Hi again,
ok so i followed your suggestion removed one condition from the radio button block (that has 3 options) so that the field is only shown if 2 of three options that share one word in their descriptiom are clicked.
Now it seems to work!
thanks in advance!
carsten