-
Notifications
You must be signed in to change notification settings - Fork 29
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
depends_on doesn't work on form fields in Fieldsets/Groups #386
Comments
Hi,
I dont know if this is a good approach, but it works for now. |
Well this template override is exactly what easyform should do with adapters. And it already does without fieldsets though so there might be some missing logic. I recently had something similar with |
Is it possible that the fix never made it to the plone5 compatible 3.X.X version line of collective.easyform |
|
The template changes for 3.x are all there. collective.easyform[patternslib] installs plone.patternslib for easyform 3.2.1. |
Ah, so -> sorry for the noise ... didn't knew that. 👍🏼 Then, this commit should definitely be backported ... |
@Nimo-19 would you mind backporting and testing it? |
or @fredvd ? |
I’m on vacation this week. I remember making an interim release earlier this year to get the on_depends to work properly, but that was already for a Plone 6.0 site. Not sure if thar also was a fieldset issue, but I think so. I can look at it when I’m back. |
I have tested the new depends_on feature to use pat-depends for interactions between fields in Plone 6.0.0rc1 and collective.easyform 4.1.1
The feature works for fields in the 'main' easyform and I see the data-pat-depends attributes being set on the fields. But as soon as you move a field into a field set the attributes disappear from the form html inputs :-/ Maybe pat-depends also has issues when fields are hidden/ or in groups, but I can't check that yet.
I suspect an interface/adapter issue between normal fields and fieldset/group fields in Easyform like we've had multiple times already with the codebase, but I couldn't find the exact location we need to register/adapt.
@MrTango @petschki any idea where this could be caused and fixed?
The text was updated successfully, but these errors were encountered: