Last modified: 2014-07-11 14:41:57 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 T69739, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 67739 - action "formedit" fails in case not valid value is present for input type "two listboxes"
action "formedit" fails in case not valid value is present for input type "tw...
Status: RESOLVED INVALID
Product: MediaWiki extensions
Classification: Unclassified
SemanticFormsInputs (Other open bugs)
unspecified
All All
: Unprioritized normal with 1 vote (vote)
: ---
Assigned To: s7eph4n
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-07-09 17:44 UTC by [[kgh]]
Modified: 2014-07-11 14:41 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description [[kgh]] 2014-07-09 17:44:43 UTC 
In case one uses input type "two listboxes" editing a page with a action "formedit" fails if no property value is detected via the chosen value parameter, e.g. "value from property" etc.

Apparently it does not make sense not to provide a selectable value for this input type, however the observed fatal (err 500) should imho not happen either. Instead the input field should just be displayed with no selectable value.

To be frank: this happens with SFI 0.7-alpha in conjunction with SF 2.5.2 and SMW 1.8.x, so this bug may already have be rectified in the meantime and is thus invalid.
Comment 1 [[kgh]] 2014-07-11 14:41:57 UTC 
I just have cross-checked with SFI 0.7.0, SF 2.7.0 and SMW 1.8.x and verified that this issue was already solved along the way, i.e. it shows the expected behaviour described above. Thus closing this as RESOLVED INVALID.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links