Form Theming & Variables

Does form rendering functions variables "injected" in the form theme block means they are also accessible in any subsequent function scope without specifically passing them during the function call?

I realize that my understanding of twig variables is limited and that's why i can't seem to understand...

Hi,

That is not directly twig variables, but how the form system works. When it renders, it has access to the form variable and it has a bunch of values inside. You can try to print {% dump %} inside a theme block and you will see everything that was passed inside.

Cheers!

Hey Cyril S.!

Sorry for the slow reply! I would do that by passing a "var" into form_widget:

<div>
{{ form_widget(form.mycollection, {
    myVar: myVar
}) }}
</div>

That's it! As you noticed, the main template and the form theme template and totally isolated. But anything you pass as the 2nd argument of form_widget (or form_row) becomes available as a local variable in the form theme template.

Cheers!

Mmm... I tried that previously but it seems not working in my case :-(

I oversimplified my issue to ask my question and, you're right, it works well in that simple case.

But, in fact, I have 4 files and 2 includes in my form:
file1 - main template (here defining theme path) > file2 - include > file 3 - include (here form_widget)
file4 - form theme template

When defining the form theme template in the included template, the theme doesn't apply and when defining the form theme template in the main template, the variable isn't transfered to the form theme template...

Hope my explanations are clear :-\
Cyril

Hey Cyril S.!

Hmm. I'll admit that I can't remember how defining form themes works when you have included templates. I can say this, however: assuming you *are* able to get the correct form theme to be called for your form, passing a variable (via the 2nd argument of form_widget()) *will* be passed to the form theme template. That's a very basic mechanism to how the form theme system works. The logic is this:

A) Symfony determines which form theme to use (and, as you know, it has a few mechanisms to do that, like global form themes and per-template form themes. This is the part where I can't remember how it works when you use include()).

B) Symfony calls the blocks it needs from the form theme template. It exposes all of the field "vars" as local variables to that block. The vars are a combination of "vars" that were set in the form class for that field (e.g. via buildView() or finishView()) + whatever you pass as the 2nd argument into form_widget().

So, I'm can't say why it's not working... except to focus first on seeing if you can get the correct form theme to be executed. Then, the vars just "should work"... hopefully ;).

Cheers!

Hey Farry,

I think what you need is the ability to add more fields of a specific type into your form.
To get a better idea you can read the docs here: https://symfony.com/doc/cur...
or watch this video: https://symfonycasts.com/sc...

Cheers!

Hey @Ralf,

It depends on situation, there is a possibility that you will need to reuse form but with different placeholder or label. In this case it will be more practical to put it in template, also important case is that it's a page styling option and it will be better to put in template so if someone will need to adjust styling or test will not search the form class. Probably it may be person who know nothing about symfony structure and how to guess where it can be.

Cheers!

I've solved:
`{% if form is defined %}

{% form_theme form with ['form_themes/admin.html.twig'] %}

{% endif %}`

Hey @Caglar

You can have a default form_theme for you entire page and only change it where you need it by defining the form_theme to use inside the template

Cheers!

Hey Stéphane,

Thank you for this report, but I think you're wrong - it should be "{{ form_row(registrationForm.agreeTerms) }}". If you look at UserRegistrationFormType - you will see exactly "agreeTerms" field that is not mapped, i.e. "mapped = false" that means it's a virtual field in form that is not mapped to User entity at all. We can't use agreedTermsAt because it's not a boolean field but a Datetime object.

Cheers!

Hey Victor,

You are right. I have written 'agreedTermsAt' into buildForm fonction of UserRegistrationFormType class.
Sorry for that.

No problem!

Glad it was not on our side, easy win for us :)

Cheers!