Hi,
A new episode of the MediaWiki podcast Between the Brackets has been
released - this one features an interview with Pau Giner, who works for the
Wikimedia Foundation as a user experience (UX) designer. You can listen to
it here:
http://betweenthebrackets.libsyn.com/episode-19-pau-giner
-Yaron
Dear Teammates,
The users of one wiki on a multi-wiki server would like to change their search stop words.
Can I do this for one wiki ? Is there a setting ? We use MW 1.29.1.
Thank you,
Lori
I don't normally advertise new releases of this extension, much less minor ones, but this concerns a security issue, so here goes...
I just released the SimpleBatchUpload extension version 1.3.2 which fixes an unauthenticated arbitrary file upload vulnerability present in the Blueimp
jQuery-File-Upload module used by this extension ([1], [2]). This vulnerability allows remote execution of code on the server.
This vulnerability affects all versions of SimpleBatchUpload < 1.3.2 on MediaWiki < 1.27.4/1.28.3/1.29.2/1.30.0. Higher versions of MediaWiki block the /vendor directory for direct webaccess, so while the unauthorized upload of files is still possible, at least they cannot be used as remote entry points, so execution of code should not be possible.
If you are using one of the affected versions, please upgrade SimpleBatchUpload as soon as possible.
Stephan
[1] https://nvd.nist.gov/vuln/detail/CVE-2018-9206
[2] http://www.vapidlabs.com/advisory.php?v=204
Hello everyone,
we are happy to announce the immediate availability of the Semantic
MediaWiki 3.0.0 release: [0]. It is an epic release bringing a lot of
new features and improvements as well as bug fixes.
## Version highlights
– Rework of the list formats as well as the template format which is now
called plainlist and used by default
– Several user interface changes to make them more intuitive and
mobile-friendly:
= Special page "Ask". It also comes with an input assistance on input
fields, a comprehensive input help (cheat sheets) and a compact view
= Special page "Browse". It also allows for the grouping of properties
= Special page "Types". The overview also includes brief datatype
descriptions
= Special page "SemanticMediaWiki". Additionally many feature pages are
provided including a tabbed view and many additional feature pages
= Property and Concept pages including a tabbed view
– Integration in special page "Search" was extended including an input
assistance on fields and the option of adaptable search profiles
– Local-specific (ICU) sorting and collation is now possible for pages
as well as values of datatype "Page"
– Query syntax was extended in many ways by:
= query markers (@deferred, @control, @annotation)
= query conditions (+depth, in:, phrase:)
= query printouts (+width=)
– Possibility to restrict query execution of expensive inline queries
whereas you may define what expensive means in your setup
– The table format was enhanced by datatable classes
– New create protection feature as part of the authority mode
– New namespace "smw/schema" allowing to define schemas for several
purposes including search profiles for special page "Search"
– New API modules "smwbrowse" and "smwtask" were added and further API
module improvements were made
– ElasticStore introduced as an still experimental alternative backend
– Several general performance improvements
– New datatype "Keyword"
See the release notes [1] for these changes and for much more
information on the many features, enhancements, changes and fixes this
release additionally brings to you. We recommend to allow some time to
explore everything about this new release.
Note that the documention on the Semantic MediaWiki is still work in
progress. However all changes documented in the release notes are
referenced to the respective pull requests which already contain consise
information about the accompanying changes.
## Compatibility changes
Semantic MediaWiki 3.0.0 dropped support for PHP 5.5 and lower as well
as MediaWiki 1.26 and lower. See also the compatibility notes [2] for
detailed information.
## Installing and upgrading
After backing up your database just update the version in your
"composer.local.json" file to "~3.0" and run "composer update --no-dev".
Remember to also update your database afterwards by running "update.php"
due to schema changes and new database tables. This is followed by
rebuilding the stored data by running "rebuildData.php". Note that
running the schema update may take quite some time as well as rebuilding
the stored data. If you would like to install Semantic MediaWiki you can
follow the installation instructions: [3].
## Contributors
At this point we would like to thank all people involved for their
incredible work making this release possible:
James Hong Kong, translatewiki.net and the translator community, Karsten
Hoffmeyer, Jeroen De Dauw, Stephan Gambke, Kumioko, Iván, Zoran Dori,
James Montalvo, Máté Szabó,
Jaider Andrade Ferreira, Josef Konrad, TK-999, Amir E. Aharoni, C. Scott
Ananian, Kunal Mehta, Peter Grassberger, Prateek Saxena, Stephan, Thiemo
Kreuz, Timo Tijhof, Toni Hermoso Pulido, ka7, matthew-a-thompson, salle,
غلامحسین حق دوست.
We also encourage your continued participation: [4].
A big thank you to all of you for using Semantic MediaWiki. We wish you
a pleasant time and a lot of success doing so.
- The SMW development team
[0] https://bit.ly/smw-300-tg
[1] https://bit.ly/smw-300-rn
[2] https://bit.ly/smw-300-c
[3] https://bit.ly/smw-300-i
[4] https://bit.ly/smw-300-p
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
Debian and Ubuntu packages of MediaWiki 1.31 (LTS) are now available.
See <https://www.mediawiki.org/wiki/User:Legoktm/Packages> for more
information on how to get them, and basic instructions for installing
(hint: it's as simple as `sudo apt install mediawiki`).
Using packaged versions of MediaWiki are a good fit for people who
just want to have a basic wiki, and not really worry about
sysadminning it.
Thanks,
- -- Legoktm
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE+h6fmkHn9DUCyl1jUvyOe+23/KIFAlu+V9oACgkQUvyOe+23
/KITnA//b0dWfKHtwItzTbtlmeObpqii9i41XR4ZPJkYoUG80mj1LhQO8vh/4xDd
dSiv33lqX3M++IpXS8KQ/ZB3mb0KcuuusKYtnKltqoDD9CJLVggI+fawt69wQzj6
zqYeJoMG8J8vH0CAYoYVbczcn2xm+yliZ7Arb0t4p+PXO4BaAl2EE6awm0X9BsjH
3X1Ij9tzTb9wVNLNq+kgPqgoIyW8WWkY7NkI5f8uuxvH41HYr4ONrXk7Y1eFr+nx
9uzjM6eXpuYZiCcp5pzBTB+Q5OPbGqvy5f2cv3IYlY4o6Tb+YSmC9SMnTVEdzUUf
vdbVRRp6lF/tcaxwsGjwNpLdsIyZ6KhEKBxIJCs6/839WsVlYZrWMun26/LdWMGi
VZm66ehrjLsexWKJOJUC8bXYiNsSUu0R/qrsROU0871UlpZEJOC6Oh2rre21kijc
gOToTYVmZpEK7UMRgjAId9LRRE/hkDZr5ChiIi/cyE3ryZXIPTuHQeHN4zYKVlaN
BDkkCZGcUYYh+0pnxRb0H5A4GWCybHPvVlC68nFHQg+aaWEcbAbRMXEJNtvfvP/2
Omq2EAvsnFkA89jbCM71PTX6i+t5vioobXwhThcoErqMOz914ed4AerMCuuXP4/z
rRThFclx0Jwa/MWcBTFPdd1N38/eAQQHAXyk/Nvq4sXDzfk83gI=
=jsxb
-----END PGP SIGNATURE-----
Hello everybody!
Some time ago, I asked this question on the Wikimedia Development Support forums [1], but unfortunately nobody answered. Mabye here on the mailing list someone can help me.
I want to change the configuration of the Parsoid service dynamically, without modifying the `config.yaml`/`localsettings.js` and restarting the service.
My use case is simple: I need _one_ Parsoid to serve multiple MediaWikis instances. And I need to be able to add new instances without the need to reconfigure/restart Parsoid everytime.
The logic would be "If the calling MediaWiki instance sends 'ABC' as a prefix, the API url of that instance will be 'https://myserver/wikis/ABC/api.php'".
I have the strong feeling that overriding the `parsoidConfig` object in `localsettings.js` will be the way to go. Am I on the right track?
Your hints and suggestions are much appreciated.
[1] https://discourse-mediawiki.wmflabs.org/t/dynamic-parsoid-configuration/775
--
Robert Vogel
Hi everybody,
I am trying to customize the dialog that pops up after pressing the
"Publish" button of the WikiEditor - see attached image.
After searching in some places I thought logical, I tried grepping the
whole "w" folder on the server but it didn't find any instance of the
sentences:
- (To be translated) Please note that all contributions to Schorenpedia
may be edited, altered, or removed by anybody with access to it.
- On the other hand, you can "watch" a page to be notified of any change
to it and changes can always be reverted if necessary.
Does anybody know where to find those so that I can translate them to
German?
Furthermore, does anybody knows why the {{SITENAME}} magic word isn't
expanded to the name of the website? Do I have to manually set it somewhere?
Kind regards,
Manu
Hi,
A new episode of the MediaWiki podcast "Between the Brackets" has been
released; this one features a conversation with freelance MediaWiki
consultant Sabine Melnicki. You can listen to the episode here:
http://betweenthebrackets.libsyn.com/episode-18-sabine-melnicki
-Yaron
Hello,
I recently moved my mediawiki install to a new server. After
confirming that database connections were successful, I'm now getting
the following error:
Fatal error: Uncaught TypeError: Argument 1 passed to
wfReportException() must be an instance of Exception, instance of
Error given, called in
/home/myaccount/public_html/wiki/main/includes/Exception.php on line
348 and defined in
/home/myaccount/public_html/wiki/main/includes/Exception.php:285 Stack
trace: #0 /home/myaccount/public_html/wiki/main/includes/Exception.php(348):
wfReportException(Object(Error)) #1 [internal function]:
wfExceptionHandler(Object(Error)) #2 {main} thrown in
/home/myaccount/public_html/wiki/main/includes/Exception.php on line
285
Has anyone else ran into this error?
Any direction is appreciated.
Thanks!
We have a couple of internal wikis that are presently 1.27 and will
soon be 1.31, that I will be moving to AWS.
So I can either (a) use a MariaDB RDS or (b) use Amazon Aurora's
version of MySQL, which is a bit cheaper.
Aurora MySQL 2.x is MySQL 5.7 compatible going forward.
So is anyone here actually running their MediaWiki off Aurora?
And is MediaWiki likely to need a MySQL version bump in the foreseeable future?
- d.