Last modified: 2011-07-24 11:39:20 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T24821, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 22821 - allow for parsing of field definition default parameter for dynamic content
allow for parsing of field definition default parameter for dynamic content
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
SemanticForms (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Yaron Koren
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-03-13 11:29 UTC by Robert Michel
Modified: 2011-07-24 11:39 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
patch for SF1.9 to allow default parsing (1.53 KB, application/octet-stream)
2010-03-13 11:29 UTC, Robert Michel
Details

Description Robert Michel 2010-03-13 11:29:45 UTC
Created attachment 7195 [details]
patch for SF1.9 to allow default parsing

Adding the possibility to parse the default value allows for more dynamic form content. E.g. the default values could be based on a SMW query.

Attached is a patch for includes/SF_FormPrinter.inc for SF 1.9.
It was tested with:
* ParserFunctions and other such extensions
* #ask queries
* sfgCacheFormDefinitions enabled

The parsing only happens once during initial display of the form, not on previews and submits.

The same approach could probably be used for the "values=" parameter, but has not yet been implemented and tested.
Comment 1 Neill Mitchell 2010-03-16 09:07:03 UTC
This is really great. The first step towards more dynamic forms. Gets my vote :)
Comment 2 Yaron Koren 2011-07-10 17:37:10 UTC
Thanks for the patch - this capability was actually added to SF in version 2.1.1, a few months ago.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links