Update to v.1.2.104 – The form has stopped working

Hello!

Could you send me a link to the form with this issue please? Also please tell me the steps to replicate the issue (like should i click something and a field in the repeater should show?)

Regards!

I cannot give a link to the form, it is on a local server.
But I can give a link to a specially created test page with the result of my testing – https://aiof-test.instawp.xyz/aiof-test/
I will try to describe in more detail the problem that, in my opinion, could break my form.
In the new form, I created a repeating field and placed 4 Dropdown fields there (S,A,B,C). The first field S has 3 values (A,B,C). If you select a value in a field of S, the corresponding field (A, B, or C) must become visible. I managed to register the necessary conditional logic for field A (Show/Hide Field Depending on Condition).
When I tried to repeat this for other fields (B,C), I saw strange behavior – freezing, disappearance of prescribed conditions, etc.
I hope you can replicate this data model.
If necessary, I can give access to the admin panel of the site.

@veganik69 Moderator note:

 Please don’t offer to send or post logon credentials on these forums: https://www.ads-software.com/support/guidelines#the-bad-stuff

It is not OK to offer, enter, or send site credentials on these forums. Thanks for your cooperation.

Sorry i probably still don’t understand, so the problem is that you were able to set up a condition for field a but when you try to set up the same condition for field b it doesn’t allow you to? Is your form designer freezing and then the condition disapears?

To make this easier, could you guide me step by step? Like

1.- Select x in field b

2.- Type x

3.- The issue occurs, i expect x to happen but y is happening

Also, If this issue happens in the designer could you export the template and send it to me so i can try in my test site please?

Ok. Let’s get it again first.
I designed the form using the plugin AIOF(v.1.2.98)
All form elements worked well.
I updated the plugin to the latest version 1.2.104 – the behavior of the form has changed. Namely: inside the repeater field, the conditions specified in the “Show/Hide Field Depending on Condition” stopped working.

On the frontend, it looks like this:

1. Form start – visually everything is ok – the starting field S (dropdown type), to which conditional logic was not applied, is displayed with all values inside the repeater field.
2. In field S from the list select the value A – the expected event is the appearance of the dependent (according to “Show / Hide Field Depending on Condition”) field A (dropdown type).
   This worked in version 1.2.98. With plugin version 1.2.104, nothing happens.
3. In the field S from the list, select other values – no reaction.
   I checked for rules for displaying the field in the form designer – everything is in place, nothing has changed, nothing has disappeared. But the dependent field does not become visible.

I assumed that this field behavior could be influenced by another conditional logic and that it was the result of an action of a certain chain of conditions.
So I decided to create a separate test form on an independent test resource on a clean system that would reproduce the described broken part of my form.
However, I couldn’t write conditional logic for all fields because of unexpected behavior from the form designer (for B and C fields).
I assumed that the unexpected behavior of the form designer and the failure of my form had a common cause.
Therefore, I described in detail the test result.
I hope this helps.

Thanks for the description, for me when i select the value ‘A’ in the ‘S’ field of the repeater the field ‘a’ is correctly showing up. Are you using the version of the plugin that is failing?

Field A is displayed in version 1.2.98
After upgrading to 1.2.104, Field A is not displayed

I see, could you export your template and send it to me please?

Sorry, but I can’t do that

Oh, could you replicate this issue in another form and send it to me? Unfortunately if i am not able to replicate the issue i won’t be able to fix it.

Ok, I’ll try to come up with something