-
Notifications
You must be signed in to change notification settings - Fork 5
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
Broken in Craft 3.7.46. #17
Comments
Also experiencing this. Don't see logs on the server or the client that would give clues to the issue(s).
|
Hi, thanks for reporting this. I'll have a look at it ASAP. |
Thanks a lot @mmikkel. Let me know if you need any version or implementation details from us. |
@parthi-me @joshuarichard I'm not able to reproduce this, so I need more info:
I'm also not seeing anything in the v3 changelog for 3.7.45.2 -> 3.7.46 that immediately jumps out as something that'd break Reasons. If either of you could DM me ( |
Hi @mmikkel , I see the dropdown field encryption is enabled in the latest Craft CMS update. This could be the reason for the above issue. I verified that before the update dropdown values are not encoded which you directly used to check against the values and displayed the respective fields. But as the values are encoded now we may need to decode and verify the values. 3.7.46 - Added craft\fields\BaseOptionsField::encodeValue(). |
@parthi-me Thanks, you're absolutely correct. So it's specifically option toggle fields (i.e. dropdowns, radio buttons and checkboxes) that are broken, on 3.7.46. I'll look into a fix ASAP. |
Should be resolved in Reasons 2.3.1. Thanks! |
Updated to Latest Craft CMS version 3.7.46 from 3.7.45.2 and it's broken the reasons plugin functionality. I can't see any obvious errors appearing, the fields with conditional rules are applied but they just don't appear in the entries.
The text was updated successfully, but these errors were encountered: