I am seeing some strange behavior regarding a wiki user's email address. When I set it to the empty string, either via PHP or MySQL, MediaWiki still seems to believe the old email address is still present. Any advice?
Background: We have a wiki extension that sets a user's email address if it's blank, attached to the hook UserLoginComplete. (It's intended for new users on their first login.) Basically:
// On login, make sure the user has a company email address:
function setUserEmailAddressIfBlank($user) {
if (!$user->getEmail()) {
$user->setEmail($user->getName() . '@mycompany.com');
$user->confirmEmail();
$user->saveSettings();
}
}
To test this function, I blanked the email address programmatically:
$user->setEmail('');
$user->confirmEmail();
$user->saveSettings();
Then I logged out and logged back in. My UserLoginComplete callback function ran, but... it failed the test of $user->getEmail() being empty. In fact, the value was still the old email address I just blanked.
Then I logged out and logged back in a second time. This time, $user->getEmail() was indeed empty and the rest of the function ran fine, setting the user's email address to username(a)company.com.
Can someone please explain:
1. Why the old email address was still present during the first logout & login?
2. What's the "right" way to set an email address programmatically, so this caching problem doesn't happen?
Thanks very much.
DanB
Does anyone mind if I create a magic word for current user's language?
It will not fragment parser cache further than it is already because
we already support {{int:}}. Note that this functionality is already
emulatable with perversions like http://is.gd/4HQPeI - would be good if
we saved users from PITA like this.
--
Best regards,
Max Semenik ([[User:MaxSem]])
Hey,
The Education Program extension I am writing has management interfaces for
courses. These are implemented as special pages:
* Special:Course/$name
* Special:EditCourse/$name
* Special:CourseHistory/$name
Now it turns out that each course also needs a discussion page. Although it
makes little sense to use regular wiki pages for the management interfaces
(ie deriving from Article) since they are not based on the page table at
all, the discussion pages should just be regular discussion pages. After
briefly discussing this with Daniel Kinzler at the SF hackaton, he
suggested I hijack some namespace and use it's discussion pages. This seems
nice if it can be made to work, but I'm having some troubles, hence this
email.
What I want to end up with is a Course: namespace that has the view, edit
and view history functionality I already created, and obviously regular
discussion pages.
Displaying the course at Course:$name I figured out to do via the
ArticleFromTitle hook, and subclassing Article. This works, but it seems a
bit ugly since Article has tons of stuff that just does not apply here. Is
there a better way to do this? I'm not sure how to go about putting in the
editing and history interfaces. How can I add namespace specific overrides
for the edit and history actions? And how do I get rid of other actions
that do not apply to courses? For example action=raw obtains text from the
page table, which does not make sense at all here.
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
There are several maintenance scripts waiting to be run on many wikis
since years ago:
https://bugzilla.wikimedia.org/showdependencytree.cgi?id=29782&hide_resolve…
The biggest offenders are:
* https://bugzilla.wikimedia.org/show_bug.cgi?id=16112 which breaks tons
of special pages;
* https://bugzilla.wikimedia.org/show_bug.cgi?id=33253 which makes the
article count on those wikis completely broken after the count method
change.
The fact that we could/should find a perfect and permanent solution for
those problems doesn't mean that we shouldn't improve the situation
given that we can.
The fact that we can't run them every month as we once did doesn't mean
that we shouldn't run them say every 5 years (which would be an
improvement) or after big changes (such as the count method).
Even the longest scripts of that sort, when run by pdhanda some months
ago, took only some days for all wikis and didn't do any damage.
Nemo
FYI, the Wikimania 2012 call for participation is out!
We encourage you to submit a talk, a workshop or panel session for
Wikimania 2012. We have a technical track throughout the conference.
http://wikimania2012.wikimedia.org/wiki/Submissions
Scholarships are also open now, should you need help with traveling to
Wikimania.
https://secure.wikidc.org/wm/schols/
Cheers,
Katie
---------- Forwarded message ----------
From: Tiffany Smith <tiffany.lmb.smith(a)gmail.com>
Date: Wed, Jan 18, 2012 at 2:07 PM
Subject: [Wikimania-l] Call for Participation - Wikimania 2012
To: "Wikimania general list (open subscription)" <
wikimania-l(a)lists.wikimedia.org>
Hi all,
We're happy to announce that the Call for Participation for Wikimania
2012 is open! During this time of reflection, please take a few
minutes to consider what topics you've been thinking about most and
how you'd be willing to share what you know with the worldwide Wiki
community.
The two most important dates to keep in mind - outside of July 12-14 -
are as follows:
Deadline for submitting proposals: 18 March 2012
Notification of acceptance: 8 April 2012
To submit a proposal, visit
http://wikimania2012.wikimedia.org/wiki/Submissions.
If you'd like to forward this message to other mailing lists or for
broader distribution (please do!), please use the Call for
Participation included below my signature line.
Thanks so much for your consideration, and, on behalf of the Program
Committee, we look forward to reviewing your proposals and seeing you
in Washington.
Best,
Tiffany
Tiffany Smith
Program Committee Chair, Wikimania 2012
tiffany.lmb.smith(a)gmail.com
--
Call for Participation - Wikimania 2012
To submit a proposal, visit:
http://wikimania2012.wikimedia.org/wiki/Submissions
Important Dates
Deadline for submitting proposals: 18 March 2012
Notification of acceptance: 8 April 2012
Overview
Wikimania conferences provide unique opportunities for the wiki
community and its sister projects (including Wikipedia, Wikibooks,
Wikinews, Wiktionary, Wikispecies, Wikimedia Commons, and Wikimedia)
to come together, share their common goals, and develop better ways to
work together on an international level. The Wikimania 2012 program
structure is designed to create multiple opportunities for conference
participants to actively engage with the subject matter, the
environment, and, most importantly, each other. Washington, D.C, can
play an important role in Wikimania 2012 as a locale that gathers
interest in government, culture, media, and academia around the
general goals of the Wikimania conference series.
In accordance with these goals and themes, the program will include
traditional conference offerings such as paper presentations,
tutorials, panels, and poster sessions; provide lounge space and
breaks throughout for participants to gather; and innovate with an
unconference day for attendees to design their own schedule and
participation around common interests. Submissions will be reviewed
and selected in advance by the program committee. Attendees are
welcome to present in the open space track of the conference,
regardless of whether their submitted presentations were accepted.
The eigth annual Wikimania will be held between 12th and 14th July,
2012 in Washington D.C. For more information, please visit the main
site.
Presentation length
Due to the extensive amount of program submissions received in the
previous years, we request your presentation be a maximum of 25
minutes, including time for questions. You may request more time,
though shorter individual presentations are more likely to be
accepted.
This does not apply for keynote speakers, panels, or workshops. 70
minute presentations must be submitted either as panel presentations
to include at least three presenters or as workshops with a clear
lesson plan.
Tracks
Tracks are used by Wikimania to organize submissions and diversify
audiences so that presentations of competing interest do not have time
conflicts. Five tracks are proposed:
Wikis and the Public Sector
The Washington, DC, location for Wikimania 2012 provides a special
opportunity for those working in the social good, policy, government,
nonprofit, and disaster response arenas to share their experience with
collaboration on a local, national, or international level. Wikis and
complementary technologies are proving to be critical in times of
crisis and in ongoing work with citizen participation in government,
as well as in long-term goals for education, public policy, social
entrepreneurship, and development in the global south and throughout
the world. This track will explore the ways that Wikimedia projects
and related activities can be used to support citizens worldwide.
GLAM: Galleries, Libraries, Archives, and Museums
This track aims to support current outreach to Galleries, Libraries,
Archives, and Museums and build enthusiasm for continued work in this
area. Presentations and panels will demonstrate effective outreach
techniques and results from ongoing activities as well as envision the
future path for these efforts. Topics of particular interest to this
track may include: wiki technology as a tool for cultural
preservation; use of wikis by museums and libraries for information
management for the public good; legal and copyright issues; use of
content in GLAM projects, education, journalism and research;
conflicts between different laws that apply to the same wiki system
simultaneously. This track may also incorporate “field trips” before,
after, or during the evenings of the conference to visit Washington,
D.C., organizations.
WikiCulture and Community
Why do people contribute to Wikimedia projects? How might the
community grow and expand while retaining its inherent cultural ethos?
This track will explore the sociology of wiki culture and community
and provide a forum for practitioners and researchers to share
insights and best practices for community management, engagement,
participation, and conflict resolution. The assessment of different
wiki cultures and demonstration of clashes and effects of those
interactions between wiki communities and chapters is relevant to this
track. A special focus will be a discussion of gaps between different
community groups, most notably related to gender and age; within this
context, submissions related to female and teenage participation,
representative roles within the community, and the use of wikis as a
tool for different gender and age group dialogues, are strongly
encouraged.
Research, Analysis, and Education
The scope of research and analysis on wikis has grown significantly in
recent years, and wikis are rapidly being introduced to educational
institutions in the course of teaching and more formally through the
Campus Ambassador Program. The scholarly atmosphere of the selected
venue creates a special opportunity for researchers working in this
area to present papers and panels to a well-informed audience.
Subjects associated with the research component of this track can
include a diverse range of topics including: technical development,
philosophy and the humanities, communications, community management
and collaboration, information science, and a broad range of other
areas. The practitioner side of this track can include: expert
participation and inviting expert contributions; Wikiversity and other
higher education wikis; wiki sources deployed and implemented in
academia and research practice; approaches to the improvement of
collaboration in research institutions and universities; and
contribution to content quality, among other areas.
Technology and Infrastructure
Technology and infrastructure play essential roles in the success of
Wikimedia projects and other uses of wiki technology. This track will
incorporate research and practice to showcase technology applications
and theories, demonstrate new uses of existing and evolving
technologies, and focus on applying technologies to meet user needs
and improve the overall user experience. Issues and areas particularly
of note in this track include: OTRS, MediaWiki development, semantic
wikis, wiki-based Augmented Reality (AR), the use of QR codes,
Wikipedia on mobile devices, Wikipedia offline, User Interface Design,
WikiLove, Liquid Thread and related technical focus points.
Lounge Space Presentations
All proposals and presentations will be welcome in the Lounge space of
the conference, whether or not they are accepted in this initial
process.
If you have any questions, please contact:
Tiffany Smith
Program Committee Chair, Wikimania 2012
tiffany.lmb.smith(a)gmail.com
Thank you very much for your consideration, and we look forward to
seeing you at Wikimania 2012 in Washington, DC.
http://wikimania2012.wikimedia.org/wiki/Submissions
--
_______________________________________________
Wikimania-l mailing list
Wikimania-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikimania-l
--
President, Wikimedia District of Columbia
http://wikimediadc.org
@wikimediadc / @wikimania2012
Hi folks,
With everything that's been going on in WMF land (SOPA + SF Hackathon), our
code review work has been falling behind. Thankfully, we've had another
great Friday in CR, which has resulted in things getting much better. As
of this writing, we only have 60 new revisions without the "nodeploy" tag:
http://www.mediawiki.org/wiki/MediaWiki_1.19/Revision_report
...and 12 fixmes. Friday seems to be a really good day for code review; it
was also a banner day two Fridays ago.
We're still behind our original projection, but we're making great
progress! We should be able to get down to zero-ish by the February 13
deployment to test2. We'll be cutting it close, but we should be able to
do it. Onward!
Rob
I've been distracted with the set up of the 1.19 Beta project so I
haven't had a lot of attention to give to code review.
And code review has stagnated.
On January 14th, a Saturday two weeks ago, we were at 144 revisions left
to review and 28 FIXMEs. Today, we stand at 100 revisions for review
and 13 FIXMEs (according to
https://www.mediawiki.org/wiki/MediaWiki_1.19/Revision_report)
A lot of this is is from my work today to set the "nodeploy" tag.
Please look over
https://www.mediawiki.org/wiki/Special:Code/MediaWiki/tag/nodeploy?status=n…
and make sure I haven't mistakenly tagged something I shouldn't have.
Another thing I did was to try make sure code was tagged usefully. Some
extension tags only had one revision, so I moved them to the
"miscextension" tag.
Finally, I made the tables in Revision_report sortable by the number of
revisions in each cell. Using this, it is easy to see that the top
three tags are "filebackend", "core", and "miscextensions"
Today, I'm handing off a lot of the 1.19 Beta concerns to other people
so I can focus on code review again. I held a couple of CR meetings
earlier this week to try to get some progress on particularly scary
sections of code, but we need to get the really big areas of unreviewed
code (things like "filebackend") taken care of ASAP so that we can get
1.19 out.
Mark.
The developers of MediaWiki, the software Wikimedia sites run on, are
wrapping up work on a new version, with hundreds of improvements and
bugfixes. Description:
https://www.mediawiki.org/wiki/MediaWiki_1.19
There is a draft schedule for deploying this software to all Wikimedia
sites in February and March. The schedule is tentative and dates are
going to shift and change. (See the "SCHEDULING" note below in this email.)
https://www.mediawiki.org/wiki/MediaWiki_1.19/Roadmap
We want to do a lot of testing BEFORE the rollout, so that we catch
potential problems before they affect readers and editors. Please help
us! We have set up replicas of your wikis and installed the latest
MediaWiki code on those replicas, so you can spot new problems in the
software's behavior:
http://labs.wikimedia.beta.wmflabs.org
Please look at
http://labs.wikimedia.beta.wmflabs.org/wiki/Special:SiteMatrix and find
wikis to test. Try reading, editing, and so on as you normally would;
treat it as a giant sandbox. If you find a problem, please report it
here: http://labs.wikimedia.beta.wmflabs.org/wiki/Problem_reports
We are especially interested in finding out about problems that affect
unique JavaScript user scripts or Gadgets, so we can help you fix them.
SCHEDULING: Now is also a good time to let us know if there are going to
be big news days or weeks in February where your community would be
especially unhappy if you had a window with no access or no editability.
For example, if there's an important national election happening in one
of the countries you serve, we'd ideally like to avoid taking your site
down for maintenance on that day.
https://www.mediawiki.org/wiki/Talk:MediaWiki_1.19/Roadmap would be a
good place to tell us that.
If you have questions, please feel free to contact us in
https://www.mediawiki.org/wiki/MediaWiki_on_IRC or via the Wikimedia
developers' mailing list at
https://lists.wikimedia.org/mailman/listinfo/wikitech-l .
Thank you.
--
Sumana Harihareswara
Volunteer Development Coordinator
Wikimedia Foundation