Form Inputs Fields

[MichaelHarmsTIB]

CKAN version
2.9.3
Describe the bug
I follow this documentation:
https://docs.ckan.org/en/2.9/contributing/frontend/templating.html#form-macros
My code:
{% import "macros/form.html" as form %}
{{ form.input("email", id="field-email", label=("Email"), type="email", placeholder=("joe@example.com"), value=data.email, error=errors.email, classes=["control-medium"], is_required=True) }}
{{ form.checkbox('agree_license', label=_(" Ich akzeptiere die Nutzungsbedingungen des Forschungsdatenrepositoriums des FID move."), id='field-agree_license', checked=false, is_required=True) }}

The E-Mail input field is a original code raw from new_user_form.html and is_required doesn't work nor my own field {{ form.checkbox ..

Expected behavior
If is_required=true and checkbox or input field is empty, the form doesn't submit.

So what is exactly to do?

Additional details
Please could someone write for the documentation more examples.

[TomeCirun]

@MichaelHarmsTIB ckan/logic/scheme.py module is incharge of which field is going to be required and which not, we are validating our forms in our actions (ckan/logic/action package) and this is one example of it:

ckan/ckan/logic/action/create.py

Line 178 in 91c9366

data, errors = lib_plugins.plugin_validate(

we are sending the data (which we are previously getting in some of our views via request.form) alongside our scheme for validation.

I think that is_required is only for decoration, it will mark the field with * so you as a user will know that this field must not be empty:)

Thanks

ps correct me if I've missed something @amercader @tino097

[MichaelHarmsTIB]

There is no table user_extra, so I have a problem so extend a form in the way I did it for a dataset.
How can I extend a form for register (new_user.html) ?

[wardi]

We don't have an easy way to extend the user form yet #6070, but some of the underlying work was done by @amercader to support storing values and can be used to extend the form with a bit of extra effort #5382

[Mohab25]

@TomeCirun maybe not the same issue but slightly relevant, having a custom scheming Select field that have "others" as an option, once selected it shows a text input that takes data from user, once there is a submit, if you logged the data it shows the custom field value, but if logged the result of package_create action or package_update action from the same data the custom field value isn't their, however it's stored in the database as {"__extras":"field_name":"field_value"}, but when retrieving it won't show it up , i've noticed if the context is logged for package create and update, it shows "plugin_extras=None", please refer to these shots for more reference:
don't want to confuse with the actual markup of the custom field, here is how it looks:

if i tried to log the submitted data, i can still see the field is there:

this is the field value showing in the database:

but the result of package_create of package_update actions won'e show the custom field data:

thank you for any help, i've actually had a similar question of stackoverflow but no one responded, saw this as oportunity for a similar issue,