Hey all,
This is a quick note to highlight that in six weeks' time, the REL1_39
branch will be created for MediaWiki core and each of the extensions and
skins in Wikimedia git, with some (the 'tarball') included as sub-modules
of MediaWiki itself[0]. This is the first step in the release process for
MediaWiki 1.39, which should be out in November 2022, approximately
six months after MediaWiki 1.38.
The branches will reflect the code as of the last 'alpha' branch for the
release, 1.39.0-wmf.28, which will be deployed to Wikimedia wikis in the
week beginning 12 September 2022 for MediaWiki itself and those extensions
and skins available there.
After that point, patches that land in the main development branch of
MediaWiki and its bundled extensions and skins will be slated for the
MediaWiki 1.40 release unless specifically backported[1].
If you are working on a new feature that you wish to land for the release,
you now have a few days to finish your work and land it in the development
branch; feature changes should not be backported except in an urgent case.
If your work might not be complete in time, and yet should block release
for everyone else, please file a task against the `mw-1.39-release` project
on Phabricator.[2]
If you have tickets that are already tagged for `mw-1.39-release`, please
finish them, untag them, or reach out to get them resolved in the next few
weeks.
We hope to issue the first release candidate, 1.39.0-rc.0, two weeks after
the branch point, and if all goes well, to release MediaWiki 1.39.0 a few
weeks after that.
Tyler Cipriani (he/him)
Engineering Manager, Release Engineering
Wikimedia Foundation
[0]: <https://www.mediawiki.org/wiki/Bundled_extensions_and_skins>
[1]: <https://www.mediawiki.org/wiki/Backporting_fixes>
[2]: <https://phabricator.wikimedia.org/project/board/5694/>
Hello,
We have a proposal to make small adjustments to the MediaWiki database
policy which would make abstract schema an explicit requirement.
Abstract schema was approved by TechCom in
https://phabricator.wikimedia.org/T191231 and now core and all WMF-deployed
extensions have migrated to abstract schema.
You can find the proposal in here. Please take a look and comment:
https://www.mediawiki.org/wiki/Talk:MediaWiki_database_policy
If there are no major objections by the end of August 2022, I will codify
this into the policy.
Best
--
*Amir Sarabadani (he/him)*
Staff Database Architect
Wikimedia Foundation <https://wikimediafoundation.org/>
Hi,
I used to announce every new episode of my MediaWiki podcast here, but I
stopped doing it about a year ago. Maybe I'll start again - but I thought
the latest episode was especially noteworthy, because it's with two of the
developers of Abstract Wikipedia (Adam Baso and Julia Kieserman), an
extremely interesting project:
https://betweenthebrackets.libsyn.com/episode-116-adam-baso-and-julia-kiese…
There's no shortage of other interesting recent episodes, though - with WMF
developers like Alex Hollender, Tyler Cipriani and Marshall Miller, people
representing organizations like the U.S. National Gallery of Art and Space
Force, and others. You can listen to all the episodes here:
https://betweenthebrackets.libsyn.com/
-Yaron
--
WikiWorks · MediaWiki Consulting · http://wikiworks.com
Hi,
the API action feedrecentchanges
(https://www.mediawiki.org/wiki/API:Feedrecentchanges) returns a feed
with HTML diffs, including timestamps. By default, these timestamps
seem to be renderd as UTC. Is there any way to change the timezone?
E.g., by passing a timezone argument to the API?
Cheers,
Kilian
Ever since the release of 1.38, I have been trying unsuccessfully to
upgrade from 1.37.x. I keep running into the same issues. If I start from
my current 1.37.x base, I get the following errors when I run update.php:
============================
PHP Fatal error: Uncaught Exception: Unable to open file
/Vector/skin.json: filemtime(): stat failed for /Vector/skin.json in
/var/www/gpf/mediawiki-1.38.2/includes/registration/ExtensionRegistry.php:182
Stack trace:
#0 /var/www/gpf/mediawiki-1.38.2/includes/GlobalFunctions.php(89):
ExtensionRegistry->queue('/Vector/skin.js...')
#1 /var/www/gpf/mediawiki-1.38.2/LocalSettings.php(305):
wfLoadSkin('Vector')
#2 /var/www/gpf/mediawiki-1.38.2/includes/Setup.php(204):
require_once('/var/www/gpf/me...')
#3 /var/www/gpf/mediawiki-1.38.2/maintenance/doMaintenance.php(96):
require_once('/var/www/gpf/me...')
#4 /var/www/gpf/mediawiki-1.38.2/maintenance/update.php(264):
require_once('/var/www/gpf/me...')
#5 {main}
thrown in
/var/www/gpf/mediawiki-1.38.2/includes/registration/ExtensionRegistry.php
on line 182
============================
It looks like it's trying to load the Vector skin from the root of my file
system (/Vector.skin.json). If I try to force it to look in the skins
directory with something like this in LocalSettings.php:
============================
$wgStyleDirectory = "$IP/skins";
============================
I get a totally different set of errors:
============================
PHP 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/gpf/mediawiki-1.38.2/includes/Setup.php:237
Stack trace:
#0 /var/www/gpf/mediawiki-1.38.2/maintenance/doMaintenance.php(96):
require_once()
#1 /var/www/gpf/mediawiki-1.38.2/maintenance/update.php(264):
require_once('/var/www/gpf/me...')
#2 {main}
thrown in /var/www/gpf/mediawiki-1.38.2/includes/Setup.php on line 237
============================
Since I haven't modified $wgBaseDirectory anywhere, including my
LocalSettings.php, I'm not sure how to interpret this. I can only assume
this variable is derived somehow. I am *NOT* trying to override my
installation root directory; I'm just trying to get the upgrade script to
see the skins directory.
The release notes for 1.38 state: " $wgStyleDirectory and
$wgExtensionDirectory – These are now set later, so can no longer be used
within LocalSettings.php unless explicitly set in that file." I have no
idea how to interpret that; this sentence barely makes any sense. I can no
longer set this variable in LocalSetings unless I set it in LocalSettings?
The documentation here is somewhat... lacking.
At this point, I was able to get my site up to 1.37.3, but I cannot move
forward to 1.38. I remember someone else posting to this list about a
similar issue a few weeks ago, but I don't think they received any
resolution. The only other possible thing I can think worth mentioning is
that I've been running MediaWiki for years now, so I have no idea what
ancient settings might still be lurking in my LocalSettings.php file that
have been retired or changed meaning over the years. I've scanned through
the file multiple times now and I can't find anything to looks out of place.
Any help would be appreciated.
Jeffrey T. Darlington
General Protection Fault
https://www.gpf-comics.com/
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