Matias Griese

I'm reopening this issue, CC @rhukster Should we fix those skeletons?

Those extra inputs must be outside of data. You still have access to them when handling the form.

Oh sorry. The unknown values are all JSON encoded. This is to allow any kind of data to be represented. In the regular forms, these hidden fields are needed as...

Also PHP has issues with numeric indexes. I would just not use numbers, but maybe prefix them with some letter.

Looks like you have something extra in the response, that likely comes from some echo.

This should be working as we're using it. But there are going to be some more related fixes in case the elements field is made toggleable.

How about adding forms to the pages like this (to the header): ```yaml forms: 'new-form-id': '/path/to/another/form:old-form-id' ``` It doesn't work yet, but it shouldn't be too hard to add support...

Are you talking about `require: true` making the form to fail?

Without `use: keys` the default and value will be like this: ```yaml my_field: - option1 - option2 ``` With keys: ```yaml my_field: option1: 1 option2: 1 ``` Default is the...

What comes to sending all the values unchecked, yes, it will revert back to the default value because of limitations in the checkbox field in HTML. However, Grav does support...