Internationalization Issue about grav-plugin-form HOT 5 CLOSED

@rhukster in your opinion should page.route include the lang code? Or should uri.rootUrl? Or should we add a separate method to Uri that returns the root url including the lang?

from grav-plugin-form.

Just for those in this situation, it's possible to avoid the 404 setting the form.action value in the YAML frontmatter of the page as the name of the route.
For example my form is in
mysite.local/en/contact (where en is the language code).
So for the file that renders the above route (i.e. form.en.md) add the value form.action: contact
For example for italian translation my route is
mysite.local/it/contatti as I have set the slug as contatti, so set form.action: contatti
And so on.

from grav-plugin-form.

page.route() should definitely not have the lang code forced.

Better option would be to use page.url() as this will prefix with the lang code. Can someone test that?

from grav-plugin-form.

So how about changing the action line in the plugins/form/templates/forms/default/form.html.twig file to:

action="{{ form.action ? base_url ~ form.action : page.url }}"

This way the base_url will have lang code if required also.

from grav-plugin-form.

@rhukster . This seems to have solved my problem as I outlined it in Gitter earlier today.

from grav-plugin-form.