Last modified: 2012-02-17 17:38:40 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 T36116, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 34116 - autocomplete on property broken in Version 2.4-alpha revision r110391
autocomplete on property broken in Version 2.4-alpha revision r110391
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
SemanticForms (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Yaron Koren
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-02-01 13:59 UTC by Neill Mitchell
Modified: 2012-02-17 17:38 UTC (History)
1 user (show)

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


Attachments

Description Neill Mitchell 2012-02-01 13:59:49 UTC
Hi.

I have in a form:

! Organisation Name:
| {{{field|Organisation Name|mandatory|autocomplete on property=Organisations}}}

Organisations is a Page property.

This does not work with revision 110391, but works with SF 2.3.2

Running on MW 1.17.2

Cheers
Neill.
Comment 1 Yaron Koren 2012-02-17 03:04:29 UTC
Is this viewable at a public URL? If not, can you look at the Javascript console using Firefox/Firebug or Google Chrome, and see if any Javascript errors appear?
Comment 2 Neill Mitchell 2012-02-17 09:35:15 UTC
Hi.

I changed to the new syntax:
{{{field|Organisation Name|mandatory|input type=text with autocomplete|values from property=Organisations}}}

and it then worked.

Time for a ReplaceText session.

:)
Comment 3 Yaron Koren 2012-02-17 17:38:40 UTC
Oh, yes - I didn't even notice you were using the old syntax. Well, the old syntax should still be supported, ideally, but it would be a PHP issue in any case, not Javascript. I think that this was fixed in SF 2.4, though - I'm marking this as "fixed"; feel free to re-open if necessary.

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


Navigation
Links