Last modified: 2011-11-15 21:10:35 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 T34206, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 32206 - Choose whether showing namespace prefix when "using values from ..."
Choose whether showing namespace prefix when "using values from ..."
Status: RESOLVED WONTFIX
Product: MediaWiki extensions
Classification: Unclassified
SemanticForms (Other open bugs)
unspecified
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Yaron Koren
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-11-04 16:28 UTC by Toni Hermoso Pulido
Modified: 2011-11-15 21:10 UTC (History)
1 user (show)

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


Attachments

Description Toni Hermoso Pulido 2011-11-04 16:28:46 UTC
I noticed when using a «using values from ...» parameter in field, you get different page results depending on "..." is namespace or concept.

* namespace: output is {{PAGENAME}} (without namespace prefix)
* concept: output is {{FULLPAGENAME}}  (with namespace prefix)

I should check for category (I guess as in concept)

I was wondering whether there could be some way to have a better control on this, without having to hack in the template itself.
Comment 1 Yaron Koren 2011-11-04 16:32:22 UTC
Yes, that was done on purpose. Which one of these would you want to change?
Comment 2 Toni Hermoso Pulido 2011-11-04 16:39:49 UTC
(In reply to comment #1)
> Yes, that was done on purpose. Which one of these would you want to change?

The issue I found is changing, let's say, "values from namespace" to "values from concept" in order to restrict the suggested values (without having to rewrite the template).

For compatibility, if I had to change any, maybe I would do in "values from namespace" to show full pagenames as well.
However, for esthetical reasons, I admit I do not like that users see prefixes in any case.
Comment 3 Yaron Koren 2011-11-04 16:48:50 UTC
Hi,

Thinking about it more, I remember my rationale for doing it this way: for "values from namespace", there's no point including the namespace, since it's known. It's true that this makes backwards-compatibility an issue, but hopefully that can be fixed using either Replace Text or an #if call in the template.

For "values from concept" and the like, not including the namespace is risky, because there can be two pages with the same name, but in different namespaces.
Comment 4 Toni Hermoso Pulido 2011-11-06 13:34:44 UTC
(In reply to comment #3)
> Hi,
> 
> Thinking about it more, I remember my rationale for doing it this way: for
> "values from namespace", there's no point including the namespace, since it's
> known. It's true that this makes backwards-compatibility an issue, but
> hopefully that can be fixed using either Replace Text or an #if call in the
> template.
> 
> For "values from concept" and the like, not including the namespace is risky,
> because there can be two pages with the same name, but in different namespaces.

You are right in both cases. I was suggesting this simply as an optional enhancement for form inputs (as a parameter: don't show, or show in case of 'value from namespaces', prefix namespace). Of course, users should be aware of the risks in the second case and this should be included in documentation.

I haven't check the code to see how difficult this could be.
Comment 5 Yaron Koren 2011-11-15 21:09:23 UTC
I think not including the namespace, if more than one namespace is possible, would be a bad idea - I'm setting this to "WONTFIX". If you want to discuss it further, feel free to write to the mailing list about it.

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


Navigation
Links