[MGNLFORM-168] Form is not i18n aware Created: 17/May/13  Updated: 17/Jul/13  Resolved: 06/Jun/13

Status: Closed
Project: Magnolia Form Module
Component/s: None
Affects Version/s: 1.4.5
Fix Version/s: 1.4.8

Type: Bug Priority: Major
Reporter: Tom Wespi Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLFORM-175 i18n email in multi step form Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

After submit with errors (not all mandatory fields) the language in the url is lost



 Comments   
Comment by Milan Divilek [ 20/May/13 ]

Hello Tom,

I tried reproduce the issue on http://demoauthor.magnolia-cms.com/demo-project/de/service/contact.html without html5 validation and it works. Can you describe in steps how to reproduce the issue?

Thanks
Milan

Comment by Tom Wespi [ 20/May/13 ]

The problem is in

info.magnolia.module.form.engine.FormStateUtil

Starts on line 113, the redirect link is not i18n aware
public static void sendRedirectWithTokenAndParameters(String uuid, String formExecutionToken, Map<String, String> parameters) throws RepositoryException, IOException {
String link = LinkUtil.createAbsoluteLink(RepositoryConstants.WEBSITE, uuid);
link += "?" + FORM_TOKEN_PARAMETER_NAME + "=" + formExecutionToken;
if (parameters != null) {
for (Entry<String, String> param : parameters.entrySet())

{ link = link + "&" + param.getKey() + "=" + param.getValue(); }

}
((WebContext) MgnlContext.getInstance()).getResponse().sendRedirect(link);
}

Comment by Milan Divilek [ 21/May/13 ]

I see. Thanks for investigation and reporting the issue. I added it into next developer iteration of form module.

Generated at Mon Feb 12 05:37:31 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.