miniform form creator - email field

[sky writer]

No problem.  All understood.  Thanks!

[Ruud]

1. When using something special for email it should also support the eleven other onput types (other than the standard text type).
I think that just makes thing more complicated. The nice thing about miniform is that you can easaly tweak what is generated by the form creator.
No plans for now to add these input types.. Sorry 

btw... the email check in html5 forms is very "simple". Input like "me@example" is seen as a valid email address (technically it is valid). So do not rely too much on the default validation.

2. Both required settings will create the mf_r_fieldname fields where the module will check if fields are not empty.
The html5 version will also add the "required" attribute that tells the browser to check.
Note that not all browsers will do this, so the module check on submit is still active too.

3. cURL is pretty standard library for hosted webspace. It seems that it is not enabled in your WBportable server.
It might be a simple setting in the php.ini to load the php_curl.dll to make it work.
There is nothing miniform can do about this.

[sky writer]

Still enjoying working with your modules, Ruud.  I have a few questions, and can't find them addressed using forum search or your site help files.

1. When I use the miniform (v 0.11) form creator, and create a field for email address, my best option is INPUTFIELD.  But when I do this, the resulting code is:

Code Select Expand

<div  class="full">
                <label for="email"><span>Email <span>*</span></span>
                    <input placeholder="Your Email" required="required" class="{EMAIL_ERROR}" type="text" id="email" name="mf_r_email" value="{EMAIL}" />
                </label>
            </div>

This works, but there is no check to make sure the text entered is formatted as an email address.  I have figured out that changing type from "text" to "email" forces the email formatting check, but I am not sure every user of the module and form creator would know that.

Perhaps you could have some sort of check for specific terms (e.g. email) in the INPUTFIELD Title or Fieldname to set this "type" automatically.  Or if it might be safer/more logical to have a dedicated "EMAILFIELD" form element.  These are just suggestions after using your great module on many sites.

If this is just user error, please let me know.

2. Could you shed some light on what the "Required Yes (HTML5)" means, as opposed to the straight "Required Yes"?

3. I tried to use the new workflow "ID below to load the form in your Miniform module", but get this error:

Sorry cURL is not installed!

I am working locally in WBPortable.  Does this feature not work locally?

Thanks!