Is there a global variable that sets the target of the site url?
The default is of course "Main Page", but I would like to point it to my server's host name. Is this a simple edit in Localhost.php?
-Rich
Getting the following errors as shown in the apache log, when trying to
access the php file from the url its throwing a 500 error
PHP Fatal error: Interface 'LocalisationUpdate\\Reader' not found
PHP Fatal error: Class 'ApiBase' not found
ProductVersion
MediaWiki <https://www.mediawiki.org/> 1.27.0
PHP <https://php.net/> 5.5.9-1ubuntu4.17 (apache2handler)
MySQL <https://www.mysql.com/> 5.5.49-0ubuntu0.14.04.1
ICU <http://site.icu-project.org/> 52.1
Lua <http://www.lua.org/> 5.1.5
Any ideas on what could be driving this?
Last call.
---------- Forwarded message ----------
From: Edward Galvez <egalvez(a)wikimedia.org>
Date: Fri, Apr 20, 2018 at 12:42 PM
Subject: [Design] Your feedback matters: Final reminder for the Wikimedia
survey
To: "A mailing list for the Analytics Team at WMF and everybody who has an
interest in Wikipedia and analytics." <analytics(a)lists.wikimedia.org>,
design(a)lists.wikimedia.org, engineering(a)lists.wikimedia.org,
labs-l(a)lists.wikimedia.org, Research into Wikimedia content and communities
<wiki-research-l(a)lists.wikimedia.org>, Wikimedia developers <
wikitech-l(a)lists.wikimedia.org>
Hi everyone,
This is our last reminder for you to complete the Wikimedia Communities &
Contributors survey.
* To those of you who have taken the survey - thank you so much! We really
appreciate your responses. *
*This survey is closing in less than three days on Sunday 22 April 2018.*
*If you are volunteer developer, and have contributed code to any pieces of
MediaWiki, gadgets, or tools, please complete the survey. The opinions you
share will affect the work of the Wikimedia Foundation. *
*Follow this link to take the
survey: https://wikimedia.qualtrics.com/jfe/form/SV_5ABs6WwrDHzAeLr?aud=DEV
<https://wikimedia.qualtrics.com/jfe/form/SV_5ABs6WwrDHzAeLr?aud=DEV>If you
have already seen a similar message on Phabricator, Mediawiki.org,
Discourse, or other platforms for volunteer developers, please don't take
the survey twice. It is available in various languages and will take about
20 minutes to complete.You can find more information about
this survey on the project page
<https://meta.wikimedia.org/wiki/Community_Engagement_Insights/About_CE_> and
see how your feedback helps the Wikimedia Foundation support contributors
like you. This survey is hosted by a third-party service and governed
by this privacy statement
<https://wikimediafoundation.org/wiki/Community_Engagement_Insights_2018_Sur…>.
Please visit our frequently asked questions page
<https://meta.wikimedia.org/wiki/Community_Engagement_Insights/Frequently_as…>
to
find more information about this survey. Feel free to email me directly
with any questions you may have.Thank you!Edward Galvez from the Community
Engagement departmentWikimedia Foundation*
--
Edward Galvez
Evaluation Strategist, Surveys
Learning & Evaluation
Community Engagement
Wikimedia Foundation
_______________________________________________
Design mailing list
Design(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/design
The only documentation I can find about what is "required" for MW is about
what is required to install it, not what is required to use it.
MW uses JS in many places, and in some of those it also has backward
compatibility for no-script users, but is that always the case? Does MW
strive to be completely functional for those who disable JS?
The question is raised because in https://phabricator.wikimedia.org/T192241
as we expanded the reliance of one of the MW extensions (namely
AbuseFilter) on JS, we got some push back. Note that AbuseFilter also
doesn't officially announce it requires JS even though it already contains
code that would not work with JS. We are considering making JS an official
requirement for AbuseFilter and would like to know how MW core approaches
the same question.
Huji
Hi everyone,
A new episode of the MediaWiki podcast "Between the Brackets" is out - this
one is an interview with Daren Welsh and James Montalvo of NASA's
Extravehicular Activity (EVA) group, who have been running MediaWiki at
their group, and elsewhere at NASA's Johnson Space Center, since 2011.
You can listen to it here:
http://betweenthebrackets.libsyn.com/episode-6-daren-welsh-and-james-montal…
-Yaron
Cross post. Reminder.
---------- Forwarded message ----------
From: Edward Galvez <egalvez(a)wikimedia.org>
Date: Thu, Apr 12, 2018 at 3:43 PM
Subject: [Engineering] Reminder: Share you feedback in this Wikimedia survey
To: "A mailing list for the Analytics Team at WMF and everybody who has an
interest in Wikipedia and analytics." <analytics(a)lists.wikimedia.org>,
design(a)lists.wikimedia.org, engineering(a)lists.wikimedia.org,
labs-l(a)lists.wikimedia.org, Research into Wikimedia content and communities
<wiki-research-l(a)lists.wikimedia.org>, Wikimedia developers <
wikitech-l(a)lists.wikimedia.org>
Hi everyone,
This is a friendly reminder about the Wikimedia Communities and
Contributors Survey.
*We have only heard from 50 Wikimedia volunteer developers. The survey will
close Sunday 22 April 2018.*
If you are volunteer developer, and have contributed code to any pieces of
MediaWiki, gadgets, or tools, please complete the survey. The opinions you
share will affect the work of the Wikimedia Foundation.
*Follow this link to take the survey:* https://wikimedia.qualtrics.com/jfe/form/SV_5ABs6WwrDHzAeLr?aud=DEV
If you have already seen a similar message on Phabricator, Mediawiki.org,
Discourse, or other platforms for volunteer developers, please don't take
the survey twice.
It is available in various languages and will take between 20 and 40
minutes to complete.
You can find more information about this survey on the project page
<https://meta.wikimedia.org/wiki/Community_Engagement_Insights/About_CE_> and
see how your feedback helps the Wikimedia Foundation support contributors
like you. This survey is hosted by a third-party service and governed by this
privacy statement
<https://wikimediafoundation.org/wiki/Community_Engagement_Insights_2018_Sur…>.
Please visit our frequently asked questions page
<https://meta.wikimedia.org/wiki/Community_Engagement_Insights/Frequently_as…>
to find more information about this survey.
Feel free to email me directly with any questions you may have.
Thank you!
Edward Galvez from the Community Engagement department
Wikimedia Foundation
_______________________________________________
Engineering mailing list
Engineering(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/engineering
Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2018.04. This bundle is The bundle is compatible with MediaWiki
1.29 and 1.30 or above and requires PHP 5.5.9 or above.
Next MLEB is expected to be released in 3 months. If there are major
changes or important bug fixes, we will do intermediate release.
Please give us your feedback at
[[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]].
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.04.tar…
* sha256sum: e8b4da822b2dcc7906e444a65e8924d8505c028c8636cdfe8d38059dc9ef1d1c
Quick links:
* Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
* Report bugs to: https://phabricator.wikimedia.org/
* Talk with us at: #mediawiki-i18n @ Freenode
Release notes for each extension are below.
-- Kartik Mistry
== Highlights and upgrade notes ==
== Babel, cldr, CleanChanges and LocalisationUpdate ==
=== Noteworthy changes ===
* Localization and maintenance updates.
== Translate ==
=== Noteworthy changes ===
* Fixed compatibility with MediaWiki 1.29 release.
* Added the 'translate' right to the 'editpage' grant. This will allow
OAuth apps to translate.
* Translation variables can now span multiple lines.
* AndroidXml file format now includes authors.
* Maintenance and performance updates.
== UniversalLanguageSelector ==
=== Noteworthy changes ===
* Fixed Ctrl-Clicking in Compact Language Links. ([[phab:T189582|T189582]])
* ULS trigger and settings are more keyboard accessible now.
([[phab:T52793|T52793]])
* Language search results are not grouped by region.
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
Hi everyone,
We are very pleased to be making three big announcements:
1. The Platform Evolution (PE) cross-departmental program (CDP) is approved in the annual plan for next fiscal year.
This PE CDP was developed with input from staff across our organization in the Audiences and Technology Working Group. Together, these staff worked to identify some of our most pressing issues while opening healthy discussions between both departments and WMDE.
Along with the other Technology programs funded in the annual plan, funding of this program represents a renewed commitment by the Foundation to the long term health of the technology that is key to supporting our mission, staff and communities.
2. We are creating the Core Platform team, a new converged platform and services team to be the focus of the Platform Evolution CDP.
We are doing this in order to better support the PE CDP and begin the hard work of re-architecting our technology stack into a more sustainable and flexible platform, in support of the Wikimedia movement strategic direction. The MediaWiki Platform team alongside the Services Platform team hold some of the most senior technologists of our community. Their skill sets and experience are vitally important for the success of the CDP so they will be moving into the new Core Platform team. We want to thank Tim Starling and Marko Obrovac for their hard work, leadership and dedication which has brought us to this point. They and their teams are doing incredibly important work to sustain our software stack day in day out while also looking into the future and guiding the reengineering of our platform to support the mission for the years ahead.
3. Corey Floyd will be joining the Technology Department to lead the Core Platform team.
In addition to day to day management, Corey will operate in the program management capacity for the PE CDP. Corey was instrumental in formulating the PE CDP, assembling the program through extensive needs analysis, synthesis, and collaboration with Foundation team members and WMDE. He brings a proven track record in clarifying stakeholder needs and translating them into amazing products.
As many of you know, Corey started at the Foundation as an iOS engineer, was promoted to manage the iOS and Android native apps engineers who worked tirelessly to evolve the open source apps into award winners beloved by millions of our users, and has been operating in an
engineering product owner capacity for the Infrastructure team within Audiences-Readers. He is known for his work ethic, thought leadership, real world experience, and collegial spirit.
Audiences will be working to backfill the duties of Corey in Apps engineering management and Reading Infrastructure product ownership, and work is already underway to close these gap in conjunction with Corey’s cutover to Technology.
We’re happy to make the Platform Evolution CDP official. And please join me in welcoming Corey to Technology, where he’ll transition on July 1, 2018. We’ll be sharing more updates about the team and the PE CDP in the coming weeks.
We are incredibly excited!
Victoria and Toby
I’ve been way too slow in updating our wikis to new versions, often because new versions reveal all the places where my custom extensions are poorly coded (by me). One thing that has been a total nightmare for me is that our biology/genetics based wikis are heavily dependent on having pages that have titles based on PMIDs. For example, in GONUTS (https://gowiki.tamu.edu), we use pages like this one https://gowiki.tamu.edu/wiki/index.php/PMID:29370269 to gather information related to a specific paper by combining citations within the wiki with information pulled in from an external web service.
This weekend I had to bite the bullet and update GONUTS and I went with 1.29.2 from 1.25, and I was shocked to find that links to those pages and creating pages with those titles was causing bad title exceptions. I traced the problem to the overlap between PMID: and an interwiki namespace, but deleting the pmid row from the interwiki table in the database didn’t fix the problem.
I finally resorted to something that I know is a terrible, terrible idea: I tweaked the code on line 337 of MediaWikiTitleCodec.php to specifically ignore matches to ‘PMID’. It works, but I’m hoping someone can guide me on how to do this without messing with the MW core code.
I also noticed something about the updating process. I made a test copy of my backend database from a SQL dump and ran the web installer pointed at the 1.25-based database. Then I copied LocalSettings.php from the old install and did testing/debugging. When I was satisfied that things were working, I edited LocalSettings.php to point the wiki to the production database and ran maintenance/update.php… and got a fatal error that was addressed in an item I found online: https://www.mediawiki.org/wiki/Topic:U26n1a1pgo0078tt <https://www.mediawiki.org/wiki/Topic:U26n1a1pgo0078tt>
So, it seems that the update from the shell doesn’t behave quite the same as the update from the web-based system. There might have also been a difference in PMID strings getting magic links, but I’m not sure if the difference was due to shell vs web on that one.
Jim Hu
Hello all,
The Code of Conduct Committee has published the list of candidates for
the next 6 months term:
https://www.mediawiki.org/wiki/Code_of_Conduct/Committee/Candidates/2018-I
If nominated, these candidates will be trusted to enforce the code of
conduct for Wikimedia
technical spaces. You can read it at
https://www.mediawiki.org/wiki/Code_of_Conduct.
Any feedback or concern about a candidate can be submitted in private
to techconduct(a)wikimedia.org
for the next two weeks, until Tuesday 2018-04-24.
If there is any need to change the candidates slate following the
community feedback,
the committee will submit a new list, and a new two weeks period will
take place.
--
For the Code of Conduct Committee,
Sébastien Santoro aka Dereckson
https://www.dereckson.be/