In formbuilder, I have a pulldown field with a number of options. When creating each option, you can fill in Option Name, and Value Submitted. However, whether I fill in my name in the name field only, or the name and value field both, the "option value" in the page source code always shows as the number of the option, not the name I've given it. (Note: this is version 0.7.3)
Is this expected behaviour? If so, what is the value field for? I'd really like to post to the field with the names of the options, not the numbers.
Thank you!
[FormBuilder] Option values not coming through?
Re: [FormBuilder] Option values not coming through?
Can anyone else who's using a pulldown confirm whether or not this is happening in their HTML source, and which version you're using? I'd really love to pin down whether this is version-specific, or config-specific, or just happening to everyone so I can decide how to work around it. Thank you!
Re: [FormBuilder] Option values not coming through?
The description is quite short, but I *think* this bug might be about this problem:
http://dev.cmsmadesimple.org/bug/view/9557
"Field Alias is not created in the output as HTML element ID" is the entire description. It`s listed as being fixed in SVN - sadly, I can`t install from non-release on my live site right now. I`ll try to find time to test on a new site, but not sure how soon I`ll be able to do that.
Any chance I could get a confirmation from someone who`s more familiar with it whether this bug does indeed match the behaviour I described?
Also - I apologize if this has been addressed elsewhere but I couldn`t find it - any update on possible next release date? Thanks!
http://dev.cmsmadesimple.org/bug/view/9557
"Field Alias is not created in the output as HTML element ID" is the entire description. It`s listed as being fixed in SVN - sadly, I can`t install from non-release on my live site right now. I`ll try to find time to test on a new site, but not sure how soon I`ll be able to do that.
Any chance I could get a confirmation from someone who`s more familiar with it whether this bug does indeed match the behaviour I described?
Also - I apologize if this has been addressed elsewhere but I couldn`t find it - any update on possible next release date? Thanks!