Extension:Page Forms/Known bugs and planned features

Below are some notable known bugs, and major planned features, for Semantic Forms.

You can also see a listing of bugs and requested features in the Bugzilla Semantic Forms listing.

Known bugs

 * Files whose names contain non-Latin characters get those characters messed up when they are uploaded via forms - the files themselves are uploaded correctly, but the resulting text that shows up in the form is incorrect.
 * There is currently a bug in Semantic Forms in which a "field" tag that ends with more than three brackets in a row will not get parsed correctly. So, for instance, the following in a form would fail: " ". If you have such a field tag, you can simply insert a space at the end to get around this bug, like " ".
 * If you use the default MediaWiki URL style, #formlink won't work with the "button" link type. Instead, you should use "post button".

Planned features

 * add support for editing sections (defined by a title with "==" around it), in addition to just templates, using a new " " tag (this feature may lead to the removal of the partial forms option)
 * more support for getting input values from external sources, adding to the existing "values from url" parameter
 * an editable-grid input for multiple-instance templates, possibly using the jqGrid Javascript library (click on "Row Editing > Input types")
 * add handling in forms for the "Sight this revision" checkbox, if the FlaggedRevs extension is installed
 * a new input type, maybe called "progressive select", based on the "Multiple Select" option found here (this may fit better in the Semantic Forms Inputs extension)
 * make use of the Validator extension for parser functions
 * testing scripts using Selenium, modeled after SMW's own usage
 * add support for editing calls to Lua modules, made using the Scribunto extension, if/when that extension starts getting widespread usage
 * allow for the use of the VisualEditor in textareas, if/when that extension is released