Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrading Umbraco Forms from 8.6.2 to 8.9.1 introduced issue with some values not being saved #695

Closed
stefanie27 opened this issue Jan 11, 2022 · 1 comment

Comments

@stefanie27
Copy link

We recently upgraded Umbraco Forms from 8.6.2 to 8.9.1 and later also to 8.10.0 to check if issue was resolved in latest version.

The upgrade caused some form submission values not being saved. This is caused by the code to consider conditions set even when the conditions are disabled.

image

Reproduction

  1. Have Umbraco Forms 8.9.1 or 8.10.0 installed
  2. On existing form or new created form, update a field with condition that can't be met. Save the form. Go back into the form field and disabled conditions and save.
  3. Submit form with all fields entered and check if the value for the field with condition (disabled) is present

Possible Solution

Update code to include check for condition being enabled.
Method IsVisible in Umbraco.Forms.Core\FieldConditionEvaluation.cs

image

@stefanie27 stefanie27 changed the title Upgrading Umbraco Forms from 8.6.2 to 8.9.1 introduced issue with values not being saved Upgrading Umbraco Forms from 8.6.2 to 8.9.1 introduced issue with some values not being saved Jan 11, 2022
@AndyButland
Copy link

Thanks for reporting @stefanie27 and for your efforts in finding the solution. I believe we've already fixed this in some other work we've done recently investigating and fixing an issue with conditions (and I can see we've found the same fix as you). The code is currently pending review but once it's passed that we'll have it out in the next patch release. I'll associate this issue with that PR such that this will be closed labelled with the release number when it's planned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants