We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
My model
class Orders extends ModelBase { .... public function columnMap() { return [ 'compra_id' => 'id', 'compra_usuario_id' => 'user_id', 'compra_endereco_entrega_id' => 'address_id', 'compra_status_com_id' => 'status_id', 'compra_formas_pag_id' => 'method_id', 'compra_valor_total' => 'value', 'compra_feita_em' => 'created_at', 'excluida' => 'deleted', 'excluida_em' => 'excluida_em' ]; } ...
My controller
if ($this->request->isPost()) { $query = Criteria::fromInput($this->di, 'Models\Orders', $this->request->getPost()); $this->persistent->searchParams = $query->getParams(); }
and my view
<form method="post" action="{{ url('a/orders') }}" autocomplete="off"> <div class="input-group"> {{ text_field('value', 'class': 'form-control input-sm', 'placeholder': 'Pesquise por nome, número do pedido ou boleto', 'type': 'number') }} <span class="input-group-btn"> <button type="submit" class="btn btn-default btn-sm"><i class="fa fa-search"></i></button> </span> </div> </form>
when I print $query->getParams() it gives me a NULL. But if i change the name of the input to compra_valor_total, the real column name all works well.
$query->getParams()
compra_valor_total
Is this a bug or a not common use case?
The text was updated successfully, but these errors were encountered:
Fixed in 1.3.0
Sorry, something went wrong.
No branches or pull requests
My model
My controller
and my view
when I print
$query->getParams()
it gives me a NULL. But if i change the name of the input tocompra_valor_total
, the real column name all works well.Is this a bug or a not common use case?
The text was updated successfully, but these errors were encountered: