-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Remove subform in subform limitation for custom fields #38178
Conversation
I think we need to consider a nesting limit to stop the UI from falling apart. |
a limit of zero - aka the current situation seems perfect to me |
didn't looked at it yet but someone already came up with the question and I hope this protection is already in the field^^ |
I think that protection is the code your deleting ;) |
I would be very happy to have this in core, personally. |
This pull request has been automatically rebased to 4.3-dev. |
This pull request has been automatically rebased to 4.4-dev. |
Alternate #43204 that appears to be more complete. |
Closing in favor of #43204. Thanks. |
Summary of Changes
Remove the limitation to select a subform as a subform field in custom fields.
There is no reason we have this limit, subforms can already be used as field of another subform.
Testing Instructions
Actual result BEFORE applying this Pull Request
It's not possible to select subform !1 in subform !2
Expected result AFTER applying this Pull Request
You can select subform !1 in subform !2 and you also can edit it