Another EmporiumPlus Custom Customer Fields Interface module issue

[lesliekirk]

It would seem that this module isn't playing nicely with a recent MMUI to CSSUI conversion. The module does exactly what it's supposed to do on the old MMUI store. If I take the code used on the old store and try to use it on the new CSSUI store, it works with one HUGE exception - the required fields don't work. As in if the field is required, if the customer doesn't file in the field they can still submit the form. On the MMUI store, the customer cannot submit the form until they fill in the field. If there was some was to natively make Custom Fields required, this would be a moot point.

For what it's worth, the same issue seems to also affect the Sebenza Custom Customer Fields module.

[PCINET - Andreas]

I know it's a pain but maybe a good time to convert to the built-in functionality. Both modules are obsolete and require to fill out a field too.

[lesliekirk]

I know it's a pain but maybe a good time to convert to the built-in functionality. Both modules are obsolete and require to fill out a field too.

That is exactly what I want to do. How do I make these fields required just like the other customer fields? I want the same error message to trigger as the default required fields do. You can see the page I'm struggling with here.

[PCINET - Andreas]

I think you can copy most of the code from the OCST template. You also need a trigger to make the field required.

[lesliekirk]

I think you can copy most of the code from the OCST template. You also need a trigger to make the field required.

The OCST page does not have the additional Custom Customer Fields, it's the trigger to make the required that is the issue. I really would prefer the trigger be the same type that is used for the Required Customer Fields. I can't find any sort of code that I can add on to. I'm looking on at the AFAD and it has some fields this page needs. Ultimately, I need the additional Custom Customer Fields to be required, to not allow the customer to submit the form without filling in the additional Custom Customer Fields and to trigger the built-in error messages when the fields are empty.

[Kent Multer]

If you get stuck, this is something that my Modulator utility can handle.

[Bruce - PhosphorMedia]

The actual form submittal error detection in Miva is so...well 1990s (sorry guys). Customers should be told BEFORE submitting form if something is not correct.

Simplest way is something like this:

<script> 
 $('#id-of-form').submit(function() {     $('.required').each(function(){         if( $(this).val() == "" ){           alert('Please fill all the fields';            return false;         }     }); }); </script>

Better would be to add a message div to each input row to place a specific message in each box and validate on each input entry. THAT would be better, but more complicated. This might be a great 'shared' project in the community to build something that can easily be applied to the common forms in Miva.

[lesliekirk]

If you get stuck, this is something that my Modulator utility can handle.

Kent, I'll shoot you an email. I like Bruce's idea of this being a "shared" project but I've got to get this fixed yesterday.

[lesliekirk]

The actual form submittal error detection in Miva is so...well 1990s (sorry guys). Customers should be told BEFORE submitting form if something is not correct.

Simplest way is something like this:

<script>
$('#id-of-form').submit(function() { $('.required').each(function(){ if( $(this).val() == "" ){ alert('Please fill all the fields'; return false; } }); }); </script>

Better would be to add a message div to each input row to place a specific message in each box and validate on each input entry. THAT would be better, but more complicated. This might be a great 'shared' project in the community to build something that can easily be applied to the common forms in Miva.

Hasn't Miva ventured somewhere into this with the Email Field on the Levels ReadyTheme? I'd like to see Miva include the ability to have required Custom Customer Fields and the ability to collect a fee with a Custom Field, but I'm off on a tangent...

[Bruce - PhosphorMedia]

it'd be hard to make an 'ad hoc' custom field required as HOW one would determine whether the requirement was meet or not would be dependent on the scope of how the field was used. That being said, I global enhancement of the HTML5 'required' attribute would be nice. (The enhancement being that the message appearance and error notification would match the Miva processed error.

This is the simplest way of requiring a field on submit:

<input type="text" name="important_info" value="" required>

On submit, if the field with the 'required' attribute doesn't have a value, the form is blocked and a popup message is shown pointing to the field. Obviously, its odd when using along side miva processed errors as the error display is different...but it does work so long as your page conforms to HTML5 protocol (which it should)

[lesliekirk]

it'd be hard to make an 'ad hoc' custom field required as HOW one would determine whether the requirement was meet or not would be dependent on the scope of how the field was used. That being said, I global enhancement of the HTML5 'required' attribute would be nice. (The enhancement being that the message appearance and error notification would match the Miva processed error.

This is the simplest way of requiring a field on submit:

<input type="text" name="important_info" value="" required>

On submit, if the field with the 'required' attribute doesn't have a value, the form is blocked and a popup message is shown pointing to the field. Obviously, its odd when using along side miva processed errors as the error display is different...but it does work so long as your page conforms to HTML5 protocol (which it should)

The use of required on the input field overrules the Miva processed errors. As in, those fields don't "light up" and the error message doesn't get triggered.

[Bruce - PhosphorMedia]

Well, sort of. One is PRE processed, the other is POST. You could simple add the attribute to ALL required inputs

[Kent Multer]

If you have validation in the browser, you probably need it done in the server too. The customer's browser may not do everything you want; and malicious users may use some sort of Web client that doesn't do the validation at all.

[Bruce - PhosphorMedia]

I suspect the problem here is the term "validation". I'm not suggesting using pre-validation as a replacement for 'code level processing' validation...just that, its better to say "hey, that doesn't look like an email address...BEFORE a customer submits a form that requires an email address. And yes, there are times when you don't want to pre-hint at what needs to be entered, but pre-validation just means (in this case) make sure folks have seen all the fields they need filled out before the hit Submit.