Last modified: 2014-01-01 17:25:40 UTC
Using a pipe symbol in an "unexpected" place in a field definition (e.g. in a parser function call) breaks the form. E.g. for a form collecting geographic regions the following field definition should just pass on the value for the parameter "structure" to the input type: {{{field|Part of|input type=menuselect|structure= {{ #generateTree:property=Part of|display=Long name }} }}}
Going through some of the older bugs now - is this one still an issue?
I can't reproduce this, so I'm assuming it was fixed at some point - marking as "fixed".