Last modified: 2010-03-07 22:45:46 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 T24756, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 22756 - Add parameter to noarticletext/newarticletext indicating if it's the current user's user (talk) page
Add parameter to noarticletext/newarticletext indicating if it's the current ...
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-03-07 16:23 UTC by Church of emacs
Modified: 2010-03-07 22:45 UTC (History)
3 users (show)

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


Attachments

Description Church of emacs 2010-03-07 16:23:07 UTC
Add a parameter to the following messages:
*noarticletext
*noarticletext-nopermission
*newarticletext

$1 should be true it it's a user or user talk page and the current user is identical to this user.
This parameter isn't used by default, but it can be utilized with ParserFunctions to add a warning when the user is editing a user page of someone else.
Comment 1 Church of emacs 2010-03-07 16:27:33 UTC
Done in r63361.
Comment 2 Umherirrender 2010-03-07 17:34:39 UTC
I am not sure, if the following should work the same way:

{{#ifeq:{{ns:2}}:{{REVISIONUSER}}|{{#titleparts:{{SUBJECTPAGENAME}}|1|1}}
 |true
 |false
}}
Comment 3 Church of emacs 2010-03-07 18:30:36 UTC
D'oh, you're right of course. Reverted my commit in r63369.
Comment 4 Bawolff (Brian Wolff) 2010-03-07 21:08:10 UTC
Doesn't  Bug 19006 suggest that that behaviour might change in the future?
Comment 5 Platonides 2010-03-07 21:12:03 UTC
Maybe add as a "noyouruserpage" message?
Comment 6 Church of emacs 2010-03-07 21:39:19 UTC
@Bawolff: That's true, I guess. In case that feature is disabled, we can add the parameter again.

@Platonides: That only works for once specific use case of this parameter. I could think of different messages for user talk pages, perhaps even a use in other namespaces (e.g. check if <username> is the current user in Project:Request_for_Adminship/<username>). A parameter is more flexible (it wouldn't be used by default, though).

I a more general matter, we should reconsider having one standard message for all namespaces. Sure, every project can use {{#switch: {{NAMESPACE}} | ... }} to include different messages, but it duplicates a lot of efforts (as every wiki has to implement that itself). Maybe we should create specific messages for some namespaces (article, talk, user, user talk, category, file) and one default message (for all other + any custom NS)?
Comment 7 Platonides 2010-03-07 22:27:57 UTC
I proposed it considering that it may be a usecase common enough, as opposed to providing different messages for each namespace + username, which most wikis may not want to perform.
Comment 8 Church of emacs 2010-03-07 22:45:46 UTC
Well, I didn't suggest to provide a different message for all namespace+username combination :)

However, I think for a newbie it'd be nice to have a message like "this is your user page, you can write something about yourself", "this is a user talk page. Use it to leave someone a message", "this is a talk page, you can discuss the article here". Namespaces is a concept that newbies are often confused of – accurate descriptions in messages could help.

The reason why those messages don't exist on every wiki is because they require some knowledge and time to set them up, not because they aren't useful. If we supply *some* of them by default, that could help. (Although I will admit that translating them would be a bit of work)

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


Navigation
Links