Hi Everyone,
We are trying to upgrade our Mediawiki from 1.36.4 to 1.38.2. After
unpacking 1.38 to /var/www/html/w, and while running update.php, we
encounter:
# /var/www/html/w# php /var/www/html/w/maintenance/update.php --quick
PHP Fatal error: Uncaught Exception: Unable to open file
/ParserFunctions/extension.json:
filemtime(): stat failed for /ParserFunctions/extension.json in
/var/www/html/w/includes/
registration/ExtensionRegistry.php:182
Stack trace:
#0 /var/www/html/w/includes/GlobalFunctions.php(52): ExtensionRegistry->queue()
#1 /var/www/html/w/LocalSettings.php(206): wfLoadExtension()
#2 /var/www/html/w/includes/Setup.php(204): require_once('/var/www/html/w...')
#3 /var/www/html/w/maintenance/doMaintenance.php(96):
require_once('/var/www/html/w...')
#4 /var/www/html/w/maintenance/update.php(264):
require_once('/var/www/html/w...')
#5 {main}
thrown in /var/www/html/w/includes/registration/ExtensionRegistry.php
on line 182
After we commented out every offending line in LocalSettings.php
(which included most (all?) added-on extensions, like ParserFunctions,
GlobalFunctions, Gadgets, Admin, SimpleMathJax, EmailInvite), we are
still left with:
# /var/www/html/w# php /var/www/html/w/maintenance/update.php --quick
PHP Fatal error: Uncaught FatalError: $wgBaseDirectory must not be
modified in settings f
iles! Use the MW_INSTALL_PATH environment variable to override the
installation root direc
tory. in /var/www/html/w/includes/Setup.php:237
Stack trace:
#0 /var/www/html/w/maintenance/doMaintenance.php(96): require_once()
#1 /var/www/html/w/maintenance/update.php(264):
require_once('/var/www/html/w...')
#2 {main}
thrown in /var/www/html/w/includes/Setup.php on line 237
Fatal error: Uncaught FatalError: $wgBaseDirectory must not be
modified in settings files!
Use the MW_INSTALL_PATH environment variable to override the
installation root directory.
in /var/www/html/w/includes/Setup.php:237
Stack trace:
#0 /var/www/html/w/maintenance/doMaintenance.php(96): require_once()
#1 /var/www/html/w/maintenance/update.php(264):
require_once('/var/www/html/w...')
#2 {main}
thrown in /var/www/html/w/includes/Setup.php on line 237
We are not setting $IP in our LocalSettings.php (as others have
suggested is a problem).
We are left to wonder... why doesn't this stuff just work? If we are
forced to upgrade on Mediawiki's cadence, the least you could do is
ensure there's an upgrade path.
We are really struggling with the upgrade problems. Any help would be
greatly appreciated.
Jeff
Hi all,
Just a small reminder for any developers that they only have 4 more
days to become eligible to vote in the 2022 WMF Board of Trustees
election.
Developers can confirm their eligibility by reviewing the below list:
* are Wikimedia server administrators with shell access
* or have made at least one merged commit to any Wikimedia repos on
Gerrit, between 5 January 2022 and 5 July 2022.
* or have made at least one merged commit to any repo in
nonwmf-extensions or nonwmf-skins, between 5 January 2022 and 5 July
2022.
* or have made at least one merged commit to any Wikimedia tool repo
(for example magnustools) between 5 January 2022 and 5 July 2022.
* or have made at least 300 edits before 5 July 2022, and 20 edits
between 5 January 2022 and 5 July 2022, on Translatewiki.
* or maintainers/contributors of any tools, bots, user scripts,
gadgets, and Lua modules on Wikimedia wikis.
* or have substantially engaged in the design and/or review processes
of technical development related to Wikimedia.
This list was copied from
<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2022/Voter_e…>.
If you need help getting a patch(/s) merged in the next few days,
don't hesitate to reach out to the community in the next few days on
the mailing lists, other locations such as the various IRC channels or
phabricator.
Regards,
p858snake/Peachey88
[If you don't write gadgets, user scripts or work on MediaWiki code feel
free to ignore this message]
Hey all!
Given the hackathon this weekend, now seemed like a good idea to talk about
us having a policy for code we write for gadget and user scripts developers
and as gadget and user script developers. TDLR: I am proposing a policy to
guide developers and authors of these kinds of scripts. I would like people
to read through my first draft
<https://www.mediawiki.org/wiki/User:Jdlrobson/Extension:Gadget/Policy#Polic…>
[1] and give me feedback on the talk page. Please feel free to share on
wiki.
*What is being proposed*
A policy page that would be editable on wiki and linked to from the editing
interfaces on gadgets, to guide both parties on how to write code that's
sustainable and less prone to breakage.
*Why is this needed?*
Despite gadgets and user scripts (which will be referred from now on as
wiki-based code) being a key component of MediaWiki projects, up until now
frontend APIs (e.g. how wiki-based code should interact with source control
provided code) have been ill-defined leading to misunderstandings between
engineers and wiki-based code developers when wiki-based code break. This
also leads to code rot, where developers do not feel empowered to make
changes as it's unclear how their changes will impact wiki-based code
developers. On top of this, when wiki-based code breaks it's not clear who
can and will fix them.
To solve this a policy I have been pushing for some time to make the
contract between MediaWiki developers and wiki-based code developers
explicit and less confusing.
I hope on the long run a policy would restore trust and good faith between
the two parties.
*How can you help?*
To contribute to the policy please use the discussion page to raise
concerns, suggestions, removals or additions.
*What's the deadline?*
I'd like to have all feedback gathered by 30th May 2022
[1]
https://www.mediawiki.org/wiki/User:Jdlrobson/Extension:Gadget/Policy#Polic…