Last modified: 2014-02-12 23:38:31 UTC
If I have a template with named AND numeric parameters, and I order my SForm to put a named parameter first, all the numeric parameters will be off. This presents itself strongest with optional named parameters along with numeric parameters in partial forms. Let's say we've got a list, where each item can be marked as 'deprecated', which is the first optional (and named parameter), with numeric parameters used for all the actual template fields to display the item. As soon as someone marks one item as 'deprecated' and edits the partial form, every {{{1}}} becomes {{{2}}} and so on, moving over the parameters of every item already entered. If they don't spot this and save the form (which at least on my wiki has happened) they then effectively destroy the display of the whole list. I reported this to Yaron in IRC a week ago, filing here for completeness and so I know when/if it ever gets fixed. I have high hopes given track history! I am currently holding off using SForms until this gets fixed, but partial forms would really make my wiki more usable to my non-technical users. I'm very excited about the future.
Changing name from "SForms misreads template parameters" to "Semantic Forms mishandles templates that have both named and numeric parameters", for clarity.
