Posted by Itangalo on October 22, 2008 at 2:33pm
3 followers
| Project: | Webform |
| Version: | 6.x-3.0-beta2 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
When creating a new form component with the same name as a previous field key, the new component gets saved with the same field key as the old one (and no warning).
An example may clarify what I mean:
Imagine having components with names "Question 1", "Question 2"... and you would then like to insert a new "Question 4". After renaming questions 4-10 you create a new component with name 4. This gets saved with the same field key as the previous question 4, and thus doesn't show up on the form.
After editing the component and opening the advanced box, a warning of duplicate form keys is displayed (when trying to save).
Comments
#1
I've finally fixed this issue (our oldest in the queue) in the 3.x version. This patch requires non-duplicate keys before allowing form elements to be moved under the same parent. As far as I can tell, the duplicate check on adding a new component has been fixed for some time. Committed to both 3.x branches.
#2
Automatically closed -- issue fixed for 2 weeks with no activity.