Symfony form read only field - symfony

Question

How should I render read-only fields using Symfony form component?
This is how I am trying to do that to no avail:
Symfony 2
$builder
->add('descripcion', 'text', array(
'read_only' =>'true'
));
}
Symfony 3
$builder
->add('descripcion', TextType::class, array(
'read_only' => 'true'
));
}

Answer 1

Provided answers all end up with this exception on Symfony 3:
Uncaught PHP Exception Symfony\Component\OptionsResolver\Exception\UndefinedOptionsException: "The option "read_only" does not exist.
The right way to do this is to take advantage of attr property on the field:
->add('descripcion', TextareaType::class, array(
'attr' => array(
'readonly' => true,
),
));
If you are after way to have a field with data not posted to the server during form submission, you should use disabled like:
->add('field', TextareaType::class, array(
'disabled' => true,
));
on your form builder object.

Answer 2

I believe the only secure method to present a form field as readonly and also prevent your form from accepting a new value in a request is the following.
$builder->add(
'description',
TextType::class,
['disabled' => true]
);
The other suggestion of using either ['attr' => ['readonly' => true]] or ['attr' => ['disabled' => true]] will leave you vulnerable to forged requests.
Both the latter options will set either readonly or disabled attributes on the field, but your Form will still accept a new value for this field if included in the request.
Only the first option above will both disable the form field and also prevent your Form from accepting a new value for the field in the request.
I have tested this with Symfony Form 3.4. I do not know if 4 behaves the same.

Answer 3

You have declared your read only attribute to a string, it needs to be a boolean.
remove the quotes around true
like this:
->add('descripcion','text',array('read_only' => true))
true, without the quotes.

Answer 4

Symfony 4 allows using only "disabled" option in form field. But it is something different that "readonly".
Disabled - user can't edit field and its value IS NOT passed during form submision.
Readonly - user can't edit field but its value IS passed during form submision.
Only solution I found for "readonly" is:
->add('fieldname', TextType::class, [
'label' => false,
'attr'=> [ 'readonly' => true ]
])

Answer 5

read_only is deprecated since Symfony 2.8. So please use readonly instead. And provide boolean value for this attribute
->add('','text',array('readonly' => true))

Answer 6

Update: since Symfony 3.0, the readonly value should be set in the attr option.
http://symfony.com/doc/2.8/reference/forms/types/form.html#read-only
The disabled option can also be used instead.

Answer 7

Would recommend using the disabled option because any submitted value will be ignored as per the docs: https://symfony.com/doc/current/reference/forms/types/text.html#disabled
$builder->add('descripcion', TextType::class, [
'disabled' => 'true',
]);

Answer 8

readonly and not read_only. You shoud make this option in attr like this:
->add('', TextType::class, array('attr'=> array('readonly' => true)))

Answer 9

Let me add something that the other answers didn't help to manage with. The treatment as field but "tweak" to disable edition may work in many cases. However, it's at least difficult to render in some formats that fully prevent edition (i.e., render as a label).
How to solve this? What I did is to define the field as HiddenType, and in the template, render using {{ form.vars.value.myfield }} or {{ item.myfield }} taking "item" as the entity object, enclosed in whatever you can think of, as any other HTML element.

Answer 10

Other solution could be:
->add('value', TextType::class, ['disabled' => true]):
Taken from: http://symfony.com/doc/current/reference/forms/types/text.html#disabled

Answer 11

Only 'disabled' option does not cause an error
$builder
->add('descripcion', TextType::class, array(
'disabled' => 'true'
));
}

Answer 12

If familia and proveedor are relations to other entity i think they shouldn't be text type. Try nullify their types or change to entity type and check if it worked.