Last modified: 2010-12-01 04:29:09 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 T27188, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 25188 - Different values (with or without prefix) using autocomplete with categories or concepts
Different values (with or without prefix) using autocomplete with categories ...
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-09-16 11:53 UTC by Toni Hermoso Pulido
Modified: 2010-12-01 04:29 UTC (History)
1 user (show)

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


Attachments

Description Toni Hermoso Pulido 2010-09-16 11:53:11 UTC
Hello,

I have the following field definitions in

{{{field|Principal_Investigator|autocomplete on concept=Principal Investigator|list|delimiter=,|input type=textbox|width=30|height=2}}}

{{{field|Contact|autocomplete on category=Clients|list|delimiter=,|input type=textarea|width=30|height=2}}}

Actually, both 'Principal Investigator' concept and 'Clients' category host only pages under 'Client' namespace (prefix).

However, when values are retrieved from autocompletion, in the first case I get them with 'Client' prefix, and in the second without.

Category Clients has default form defined and I tried to put in Concept as well, but no change.

This is not critical, because I can play with the templates in the end, but should not be the same behaviour in both cases?
Comment 1 Yaron Koren 2010-12-01 04:29:09 UTC
Indeed, the behavior should be the same - the namespace now shows up with "autocomplete on category", in v2.0.6.

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


Navigation
Links