[MGNLFORM-65] The values of the form selection (formSelection component) are shown in the contact mail. The labels should be displayed always. Created: 10/Nov/10 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia Form Module |
| Component/s: | field, mail |
| Affects Version/s: | None |
| Fix Version/s: | 1.4.x |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Diana Racho | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | next | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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: |
| Comments |
| Comment by Federico Grilli [ 11/Jan/11 ] |
|
This issue too seems to have gone with form module version 1.2. Can be verified online e.g. at http://demoauthor.magnolia-cms.com/demo-project/service/contact.html |
| Comment by Federico Grilli [ 11/Jan/11 ] |
|
Fixed by release 1.2 |
| Comment by Federico Grilli [ 11/Jan/11 ] |
|
Well, I read the issue too fast. Actually this behavior needs to be verified. |
| Comment by Federico Grilli [ 11/Jan/11 ] |
|
This patch does the job but should be reviewed as I'm not sure about it. Basically, I added a couple of fields to info.magnolia.module.form.engine.FormField so that, when a form processor is going to be executed, I know if the current field is a "selectable" one (checkbox, select or radio button). In that case info.magnolia.module.form.engine.FormStepState.getValues() will get the labels of the selected values instead of the values themselves. However, while this can be reasonable for the form mail processor, perhaps it's not what one would expect for other processors. |
| Comment by Federico Grilli [ 12/Jan/11 ] |
|
replaced patch.txt |
| Comment by Tobias Mattsson [ 13/Apr/11 ] |
|
I think we need more details on the use case. It's perfectly possible to let value and label be the same string. In even possible to type in just the labels, because the values will default to the respective labels. For example in the example 'Call for Papers' in demo-project there's a select named 'track' containing only the labels 'Technical Track' and 'Business Track'. These are submitted as track='Technical Track'. |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |