Glitch Form Radio Button which setting the server is responsible for handling the variables in the template engine?

Question

Glitch Form Radio Button which setting the server is responsible for handling the variables in the template engine?

7 views

At some point I'm getting the weirdest glitch:
the standard syntax

{{ Form::radio('somename', 'someval', true, ['adparam'=>'someparam']) }}

option checked does not work on localhost (mac vagrant/box, laravel 5.4), but works on remote server...
Already broke all head, in what side to dig, as it didn't even notice the time when the off function (the fact that it worked to a certain point - the fact)?

UPD:
After dancing with a tambourine, it turned out that servers at different process values.
For localhost it works:

{!! Form::radio('sex', 0, true) !!} {!! Form::radio('sex', 1) !!} {!! Form::radio('sex', 2) !!}

for production servers:

{!! Form::radio('sex', '0', true) !!} {!! Form::radio('sex', '1') !!} {!! Form::radio('sex', '2') !!}

The question of where hidden paramenta processing variables etc (1!='1')?

asked Apr 13, 2019 by O_Nayre | 7 views

1 Answer

Tesla · Answer 1 · 2019-04-18T17:59:17+0000

The problem was in different versions of the PDO drivers and correspondingly different processing of int/num/str, a temporary crutch:

'mysql' => [ ... 'options' => [PDO::ATTR_EMULATE_PREPARES => true] ],

More stackoverflow
Thanks to the community Laracasts.

Glitch Form Radio Button which setting the server is responsible for handling the variables in the template engine?

Please log in or register to add a comment.

Please log in or register to answer this question.

1 Answer

Please log in or register to add a comment.

Related questions

Most popular tags