#1568 Correct use of name/value attributes for project registration
Right now the project registration form renders the checkboxes like so:
<input type="checkbox" name="Tickets">
Checkboxes that are logically grouped should all have the same name attribute while having different value attributes:
<input type="checkbox" name="tools" value="Tickets">
This ticket compliments [#1567] and should probably be implemented at the same time, as it's cleaner when there's just one checkbox for an SCM tool rather than checkboxes for each SCM.
Code is on allura and forge-classic js/1568. This isn't actually working yet, but I'm sending this to you for your thoughts. Do you think I'm using EW the right way here? I have the form mostly working how I'd like (I need to make the selected based on form value, not hardcoded, for instance), but the validation doesn't seem to be right. When I submit the form with multiple checkboxes checked, I only see the value of the last one checked in the controller (the log message in project.py). I see we haven't ever used CheckboxSet in allura and the test in ew doesn't actually test validation, is it possible this hasn't ever worked right? Or maybe I am using it wrong and need to try a different approach?
The problem was a bad interaction between our variabledecode filter and antispam filter. I pushed a fix to your branch and send the ticket back to you :)
Ok, the form should work now. To test, make sure you can register a project with whatever tools you select and the html looks like described above.