mForm | mForm helps you to make your forms and form elements | Form library

You need to first prevent the form from submitting and check place.geometry the way you check it on place_changed event. Show that nice swal message and then do whatever you want to if it's valid.

Here below is your own codes edited and checked before submit.

I see that you have commented and slightly modified the Form type alias declaration compared to what is in the blog. You need this line somewhere in your code in order to define what Form is:

The selectField function takes an OptionList a representing a selection from a list of Haskell objects of type a. The OptionList a is a list of Option a values that combine a Text user-facing label, the a value being selected, and the Text for the HTML-level value that will be returned by the client in the form. The selectFieldList function is a specialization that uses increasing integer labels for the HTML-level values, which is why you are seeing a series of increasing integers instead of meaningful values returned by your form.

So, you want to use selectField in place of selectFieldList. That's not the end of the story though. As I understand it, you are trying to render a form with a dynamic set of choices (presumably generated monadically from a database query). When the form is posted, you are hoping to receive a meaningful HTML-level value, so that you can accept and act on it statelessly without needing to remember the original dynamic set of choices. That way, you can bypass runFormPost and act on the returned value directly.

In general, this is a bad idea! By bypassing runFormPost, you are bypassing cross-site request forgery (CSRF) protection and form validation. This might work for your specific case, if you have only a single field in your form, take care to validate the returned HTML-level value manually, and do your own CSRF mitigation (or are operating in a trusted context where this isn't an issue). But, a more general solution is possible, though it's a little hacky.

Let me use a self-contained example to illustrate. For your dynamic drop down, for each option there will be three values involved, the internal City type at the Haskell level (e.g., your PG.DbCity), and two Text values: a user-visible label that appears in the drop down menu, and a self-contained Key that will be sent in HTML-level value attributes and passed back to you to validate and convert back into a City.

So, you've got, say:

I think the problem is that you form's model is post and you're assigning object of user as instance.

So try this way:

The problem is that ambiguityForm is an AForm, but generateFormPost expects an MForm. To convert it to an MForm suitable for rendering, you need to use renderDivs, like you did in your locationForm example. You can either do this in the definition of ambiguityForm, which will change its type/defintion to look something like:

The files are stored in request.FILES:

Great that you are using the proper like functions!

For the SQL, you need to use a separate where for each union rather than at the end. You were also using u.id = $id which would have restricted it to one user id.

So I've reworked your SQL - this should work.

The duration field is a group of fields

• A text field named number
• A select field named timeunit
• A checkbox field named enabled

See /lib/form/duration.php

So maybe try

For those who need it, I found a solution.

We apparently cannot add our own css class directly on select in moodle 3.7 but this class is added on a div surrounding the select, so I change a bit my style.css class to take that into account.