divio
Form Fields should only be placeable as an descendant of the Form plugin
Reopened due to https://github.com/aldryn/aldryn-forms/commit/3231d76b45cdb72301e91ac747e11dffa5d2b69f
Is that means that we can place field under form but in several levels of containers?
Yes. This doesn't mean that fields can't have multicolumn or other plugins as parents, this means that fields should always be descendants of the form plugin, doesn't matter where in the tree.
Could this be reverted to 467adbd commit, because it causes more problems than it solves? If you, by accident, place form field outside the form plugin (which is now possible), it causes database error.
Reverting to that commit would be a major backwards incompatible change and not really aligned with the design of this app. There are more occurrences of users adding non-field plugins under the form than users adding the form fields accidentally outside the form.
Ok. Good to know. I'll keep using my fork. Just asked because this actually happened, and it could only be fixed by manually removing entries from database.
On cms 3.5 we're introducing the ?structure GET parameter which is for structure-only view, hopefully this makes it easier to correct these issues without having to do so manually on the db.
I am afraid that idea of placing field only under some form plugin is not good. There may be cases where the user wants to place the field outside the form. And input outside form is perfectly html valid code.
https://validator.w3.org/:
<!doctype html>
<html lang="en">
<head>
<title>Title</title>
</head>
<body>
<input>
</body>
</html>
