Last modified: 2014-04-29 14:40:43 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 T23318, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 21318 - Switch new user welcome message to manually hidden talk page box
Switch new user welcome message to manually hidden talk page box
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Low enhancement with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-10-27 22:40 UTC by Equazcion
Modified: 2014-04-29 14:40 UTC (History)
9 users (show)

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


Attachments

Description Equazcion 2009-10-27 22:40:08 UTC
Currently, newly registered users are shown Wikipedia's welcome message (MediaWiki:Welcomecreation), including general rules, only once. When the user navigates away, the message is lost. Based on the discussion at Wikipedia:Village_pump_(proposals)#MediaWiki:Welcomecreation_-.3E_Welcome_notice, there is consensus that this functionality should be changed, as currently the welcome message likely goes unnoticed by most users, since it so easy to inadvertently remove it from view permanently.

The message should instead become a box that appears when the user views their talk page; It should NOT, however, be an actual talk page posting; ie. the welcome message should not actually cause creation of the talk page, and links to the new user's talk page should remain red. The message should be dynamically hideable via a "dismiss this message" link. The message should be placed either below the talk page's main header (its title), or in the sitenotice location; whichever seems more technically and aesthetically feasible. 

Some technical changes the proposer foresaw in the discussion are as follows:
a) turn off MediaWiki:Welcomecreation
b) create MediaWiki:Welcomecreation2 as the new welcome message, to be shown to new users at the top of their user talk page until they dismiss the message
c) turn MediaWiki:Welcomecreation2 on

Thanks! Please post any questions if further clarification is required.
Comment 1 Rd232 2009-10-27 22:58:52 UTC
Backward compatibility is envisaged, hence the addition of variables allowing individual software installations to choose whether to show the old message or the new one.
Comment 2 Equazcion 2009-10-27 23:02:24 UTC
(In reply to comment #1)
> Backward compatibility is envisaged, hence the addition of variables allowing
> individual software installations to choose whether to show the old message or
> the new one.
> 

I posted this as a Wikimedia bug rather than MediaWiki, but feel free to switch that if appropriate.
Comment 3 Rd232 2009-10-27 23:03:26 UTC
Also, in case it wasn't clear, the new "MediaWiki:Welcomecreation2" would be
shown at the top of the user talk page until dismissed; and if the appropriate
variable is set, users will be taken to their user talk page after account
creation, hence seeing that message, instead of being shown
"MediaWiki:Welcomecreation".
Comment 4 Nemo 2011-04-25 10:34:02 UTC
I disagree with this request.
We shouldn't mix up temporary (system) messages and permanent (talk) messages. If you want a user talk message, just add a user talk message as everybody does (and English Wikipedia does not for unknown reasons). There's even the NewUserMessage extension for that.
Comment 5 Rd232 2011-05-01 21:57:25 UTC
@Nemo_bis

English Wikipedia doesn't do it because people want to preserve the ability to easily identify new accounts by virtue of them having redlinked user and/or user talk pages. 

As for the "mixing" - there is no mixing, because the point is precisely that it should not create a talk page if one does not exist, or to add it if it does.
Comment 6 Nemo 2011-05-02 08:07:35 UTC
(In reply to comment #5)
> As for the "mixing" - there is no mixing, because the point is precisely that
> it should not create a talk page if one does not exist, or to add it if it
> does.

This is not the purpose of system messages and it wouldn't work properly (can you name a single message used in that way?).
Comment 7 Rd232 2011-05-08 21:04:27 UTC
At this point you understand what is being asked and why. How would you suggest it be achieved? (And how can you can claim "it wouldn't work properly" without explaining why?)
Comment 8 Krinkle 2011-05-08 21:18:01 UTC
I think the idea presented here is great.

Although I may be interpretating it differently then intended.

Two facts:
* When users have a new talk page message, they see (orange) <div class="usermessage"/> message. Once visited/read it dissapears
* When there's a new sitenotice, logged-in users can dismiss it after reading

My version of the presented en.wiki idea in this bug, in addition to the above two facts:
* When a user registers there's a welcome-notice with information new users should know (ie. "MediaWiki:Welcomecreation2"[1]). This is dismissable and won't be shown anymore after dismissed[2].

--
Krinkle

[1] MediaWiki:Welcomecreation2 isn't an acceptable message-key though, it would have to be something more descriptive and less temporary. Something like "newuser-welcomenotice" or "userregisterednotice", or plain "Welcomenotice" etc.
[2] I don't think the Dismissable-sitenotice-extension's javascript and the core sitenotice script are usable for this, since that would mean sending the welcome-notice html for everybody until the end of time, and hiding it via JavaScript based on a cookie. Instead this should probably be the other way around, based on a cookie, send it, otherwise don't (cookie could be send when signing up. So when registration is succesfull, set cookie and redirect to whereever. )
Comment 9 Equazcion 2011-05-08 21:20:35 UTC
(In reply to comment #7)
> At this point you understand what is being asked and why. How would you suggest
> it be achieved? (And how can you can claim "it wouldn't work properly" without
> explaining why?)

Echoing RD232's sentiments above. To reiterate, the goal is a dynamically dismissible message for new users that doesn't actually post data to any of their pages, and reappears whenever the user navigates to their user space until dismissed. 

If a system message isn't feasible for this, kindly detail why and offer your opinion on how best to achieve it. Thanks.
Comment 10 Nemo 2011-05-09 07:11:52 UTC
(In reply to comment #9)
> If a system message isn't feasible for this, kindly detail why and offer your
> opinion on how best to achieve it. Thanks.

See comment 4.

Krinkle's suggestion of a "welcome sitenotice" is interesting, although it seems a bit obtrusive (unless you keep it very short) and it wouldn't replace user talk welcome messages.
Moreover, we would need to investigate how many users don't understand how to dismiss the sitenotice and live with it although very annoyed (I guess they're a lot), or some automatic expiration would be needed.
Comment 11 Bawolff (Brian Wolff) 2011-05-09 07:31:55 UTC
You know, if we had some equivalent to lqt's special:newmessages in core, this would fit perfectly into that model.

Some of the comments on r66438 about sending system->user messages come to mind (that of course is a totally separate issue, but this bug report reminded me of that discussion)

(Also, while I'm here I'd like to say in regards to the original request, a big +1 to comment 4)
Comment 12 Dan Garry 2014-04-29 14:40:43 UTC
The Growth team is designing and implementing a proper onboarding process for our users. Hopefully they should be able to accomplish the intent of this bug (i.e. "onboard our new users properly") without us having to give users persistent messages.

Any questions about onboarding can be directed to Steven Walling (swalling@wikimedia.org).

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


Navigation
Links