PHP + jQuery .validate issue -

-

ill try , make clear possible. have contact form on page , remote php file "random.php" generates 2 random numbers:

<?php     $randomnum = rand(0,9);     $randomnum2 = rand(0,9);     echo $randomnum . ' + ' . $randomnum2;     $randomnumtotal = $randomnum + $randomnum2; ?>

the parent page calls such:

$(function() {     $.get( 'php/random.php', function ( data ) {     $('#resetnumbers").val(data);     });

and has input:

<input type="text" class="numbers" name="resetnumbers" id="resetnumbers" value=""    size="6" readonly>

no problems point, php file output's 2 random numbers , displayed on page. here's problem: have second text box have add 2 numbers make validate.

<input type="text" class="numbers" name="resetmath"  id="resetmath" size="6" maxlength="6" tabindex="27">

it never works. says not added correctly. here relevant part of validation rule in remote file:

resetmath: {     required: true,      equal: <?php echo $randomnumtotal; ?> }

since in remote file (don't want validation rules on parent page) doesn't seem getting same numbers. how unscrew mess?

resetmath: {     required: true,      equal: <?php echo $randomnumtotal; ?> }

doesn't seem right. should be:

resetmath: {     required: true,      equalto: $('#resetnumbers') }

the api here.


Comments

Post a Comment

Popular posts from this blog

c# - Is it possible to remove an existing registration from Autofac container builder? -

-
something along lines: builder.registertype<mytype>().as<itype>(); builder.registertype<mytype2>().as<itype>(); builder.deregistertype<mytype>().as<itype>() var container = builder.build(); var types = container.resolve<ienumerable<itype>>(); assert.istrue(types.count == 1); assert.istrue(types[0].gettype == typeof(mytype2)); scenario: go through bunch of assemblies , go register types want make sure have 1 implementation of given type. need before create container. track on own nice if autofac me bit. this cannot done directly using containerbuilder , unless start on new one. mind you, having first built container should able construct new container filtering away unwanted types , reusing registrations first container. this: ... var container = builder.build(); builder = new containerbuilder(); var components = container.componentregistry.registrations .where(cr => cr.activator.limittype != typ...
Read more

c++ - Warning : overflow in implicit constant conversion -

-
in following program, line 5 give overflow warning expected, surprisingly line 4 doesn't give warning in gcc: http://www.ideone.com/u0bxn int main() { int = 256; char c1 = i; //line 4 char c2 = 256; //line 5 return 0; } i thinking both lines should give overflow warning. or there i'm missing? the topic led me experiment this: typedef type checking? there said following(which deleted answer, because when run it, didn't show had expected): //however, you'll warning case: typedef int t1; typedef char t2; t1 x = 256; t2 y = x; //possible overflow warning! (but doesn't give warning :() -wall doesn't include many options. -wconversion 1 of them , warns behavior you're interested in. see http://gcc.gnu.org/onlinedocs/gcc/warning-options.html
Read more