Form Rendering Functions: form_*

Not sure if that's the correct part of the series, but I've got a problem with my Form.

$form = $this->container
			->get('form.factory')
			->createNamedBuilder('form', FormType::class, null, $defaultOptions)
			->add('HOOK_URL', HiddenType::class, ['block_prefix' => '', 'data' => $this->generateUrl('launcher', [], UrlGeneratorInterface::ABSOLUTE_URL)])
			->setAction($host.$uri)
			->setMethod('POST')
			->getForm();

This will render to <input type="text" id="form_HOOK_URL" name="form[HOOK_URL]" but I need it to be <input type="text" id="form_HOOK_URL" name="HOOK_URL" (without the form[] part in the name)

The form submit IS NOT handled by the controller that created the form, it's a complete different URL/endpoint that doesn't "understand" from[HOOK_URL], only HOOK_URL.

Hey Sebastian-K,

Yes, you need to override the form type's block prefix, i.e. getBlockPrefix() parent method in your form type. I'm not sure how to do this on the fly with your code, seems you're trying to do this with that "block_prefix" option, but IIRC that option does not available for fields, it should be applied to the whole form, not to a separate field. Try to apply that option in $defaultOptions maybe, but Probably better to create a separate form type for this and override it there like we did in this screencast: https://symfonycasts.com/screencast/javascript/post-proper-api-endpoint

UPD: Actually, that "block_prefix" does exist for fields, but from the docs I see it's always null anyway, so you're not changing anything with this code, see https://symfony.com/doc/current/reference/forms/types/form.html#block-prefix - it seems like it works the opposite, it's always empty but you can add some prefix for the field. I believe you need to apply that "block_prefix" to the whole form instead, not to the specific field as you did.

I hope this helps :)

Cheers!

Hi Ryan and team,

my comment is more related to this course than video but I am looking for help or suggestions.

We have clients who call the same thing with different names. It is just lets say 5 fields out of 100 currently but as application grow there will be more and more of such fields. For simplicity I will just throw here similar example. Imagine you have an entity called Dog and you are allowing your users to enter their name and age and you will also generate onscreen report and pdf copy.

1st client wants to see on the input screen Enter dog's name & age and 2nd one wants to see Enter puppy's name & age.

So currently I have in code something like If the client is 1 then label = dog else puppy.

I am wondering if I could somehow use translation for this otherwise above code is randomly placed into controllers, form types and templates.

I would like to achieve something like I have list of all those 100 fields in text file and once the client and label is detected I have prepared a translation for it but not per language but per client if that make sense. Issue is that it needs to be not just labels in forms but also readonly version or in script that is generating pdfs of your entities so as you can imagine currently it is still manageable since it is just 5 fields but I am afraid it will be more an issue once we will get more clients and they call internally same thing differently then other clients.

How would you handle this?

Hey Peter K.!

That's a fascinating challenge :). So... somehow using the translator also came to my mind... though I don't think we want to mess with the locale and start faking that client1 speaks "client1" language and client2 speak "client2" language and so has translations inside messages_client2.yml. That would be the quickest and dirtiest way to get this done, but I think it may have side effects (e.g. it may confuse a 3rd party bundle that does have translations... but maybe not... it just seems odd).

What I would probably do is add my own, tiny "client translation" service that would have, for example a public function translate(string $message): string. Internally, you would look up the current client and find their translation. The trickiest detail will be that you'll need to call this service each time you need to translate something. I would, at least initially, "be ok" with doing this - e.g. inject this service into your form classes, call this method, and pass the final string to the label. It's... kind of beautifully boring and simple :p.

For the translation files themselves, you could use any format - but if you use something like YAML, then you may just want to inject a cache service so you only parse those files once per deploy (use the cache.system cache service, which automatically clears on deploy).

Let me know what you think :).

Cheers!

Hi Ryan and team,

my comment is more related to this course than video but I am looking for help or suggestions.

We have clients who call the same thing with different names. It is just lets say 5 fields out of 100 currently but as application grow there will be more and more of such fields. For simplicity I will just throw here similar example. Imagine you have an entity called Dog and you are allowing your users to enter their name and age and you will also generate onscreen report and pdf copy.

1st client wants to see on the input screen Enter dog's name & age and 2nd one wants to see Enter puppy's name & age.

So currently I have in code something like If the client is 1 then label = dog else puppy.

I am wondering if I could somehow use translation for this otherwise above code is randomly placed into controllers, form types and templates.

I would like to achieve something like I have list of all those 100 fields in text file and once the client and label is detected I have prepared a translation for it but not per language but per client if that make sense. Issue is that it needs to be not just labels in forms but also readonly version or in script that is generating pdfs of your entities so as you can imagine currently it is still manageable since it is just 5 fields but I am afraid it will be more an issue once we will get more clients and they call internally same thing differently then other clients.

How would you handle this?

Hi,

I have weird behaviour.

I am using 2 forms on 1 twig template.

I will create 2 forms in controller and pass them to template.

<br />'form1' => form1->createView(),<br />'form2' => form2->createView()<br />
then in controller when the forms are submitted i check (there are being check in one route)
if form 1 is valid then do this and that
if form 2 is valid then do this and that

everything works so far ok.

Now if I submit only form1 with some blank fields so it will return validation errors, it will also throw errors on form2

so in my twig if I check
<br />form1.vars.valid will return true -> as expected<br />form2.vars.valid will return true -> never been submitted<br />

so I decided to check if in twig if form has been submitted and I added
<br />form1.vars.valid and form1.vars.sibmitted -> returns true as expected<br />form2.vars.valid and form2.vars.submitted ->returns true it hasnt been submitted.<br />

so the question is why are both forms being submitted if I submit only 1

to be added in twig I am properly starting and ending each form

`
{{ form_start(form1) }}
{{form_widget(form1)}}
<button type="submit">.....</button>
{{form_end(form1)}}

{{ form_start(form2) }}
{{form_widget(form2)}}
<button type="submit">.....</button>
{{form_end(form2)}}
`

Possibly Ive solved it so this is just a future reference for someone with this issue.

The issue is that the forms had the same name when creating them in controller.

so you either need to create form class for each form and give it different name or when creting form in controller to use

$form1 = $this->get('form.factory')->createNamedBuilder('form1')->add(......

Probably another issue is that both forms have the same action URL. It may cause problems