Welcome to SMWCon Fall 2019 in Paris from September 25th to 27th 2019!
In the name of our host UIC, the worldwide railway organization , our
general chair Airy Magnien and our local host Clément Flipo, I would like
to set the stage for our upcoming conference with a syllogism:
1. We believe that Semantic MediaWiki is a premier knowledge collaboration
2. It is a fact that successful systems are used voluntarily. Because the
marginal utility they endow far outweighs the marginal cost of adapting to
3. It is therefore our chief concern to facilitate a smooth, intuitive and
pleasant use, operation and setup of Semantic MediaWiki.
== Registration is now open! ==
For general information including dates, location, registration,
accommodation and travel information please go to the official conference
== Call for contributions! ==
Please check the program section for suggesting or taking over talks,
tutorials, workshops, create camps or posters. 
For any further information you can contact us at smwcon(a)mwstake.org.
Thank you and we are looking forward to welcoming you in Paris!
Sorry for cross-posting.
---------- Forwarded message ---------
From: Kosta Harlan <kharlan(a)wikimedia.org>
Date: Tue, Jul 16, 2019 at 10:28 PM
Subject: [Wikitech-l] Changes and improvements to PHPUnit testing in
Please have a look at
regarding some significant changes and improvements to the PHP testing
tools included with MediaWiki.
Your feedback and contributions are most welcome, either here, on phab, or
on IRC (Amir1 and kostajh in #wikimedia-codehealth). One of us should be
around during the technical advice IRC meeting tomorrow as well if you have
questions about how to port your tests, run Amir’s script, or have
suggestions / feedback.
Kosta & Amir
Wikitech-l mailing list
This announcement is about 24 hours late, but: a new episode of the
MediaWiki podcast came out yesterday, featuring an interview with Bryan
Davis, who is head of the Cloud Services team at the Wikimedia Foundation.
You can listen to the interview here:
I will be out of the office until Thursday, August 1st, without access to voicemail or email. I will respond to all messages upon my return.
Marketing and Special Technical Services Manager
I have recently completed an upgrade from MW29 to the latest MW32
release. During the course of the upgrade 3 pages were created/edited
after the database schema but before the rest of the installation had
been upgraded to MW32. These 3 pages now return the following error:
MediaWiki internal error.
Original exception: [XR38GZC0pLP1U7uAGwvs1wAAAAA] 2019-07-04 13:16:09:
Fatal exception of type "MediaWiki\Revision\RevisionAccessException"
Exception caught inside exception handler.
Setting $wgShowExceptionDetails=true produces a lot more info which I
can post if necessary but the above message makes me suspect that there
is an access key involved. I'm thinking this could be because the
upgraded installation was transferred as a tarball from a different
server so that just the server details in LocalSettings.php then needed
to be changed.
Can anyone offer any pointers or advice on how I might best resolve this
I'm seeing an issue with VE on a MW system that uses a remote SSO. While MW itself work well with the SSO, VE has the following issue:
* SSO session expires (unknown to the client)
* Client attempts to edit a page using VE
* Server redirect client to SSO for revalidation
* SSO refuses to process request due to the following error - "... blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource."
* Client gets VE "Something Went Wrong" message
* SSO cannot be configured to change CORS policy
Can VE be updated to meet the SSO CORS Policy?
I'd imagine setting up a wiki farm in a Windows Server environment with IIS
would be similar to Linux/Apache environment.
What are some best practices for setting up a wiki farm in a Windows Server
environment? For use in an intranet-only environment.
I'm leaning toward the Multiple wikis sharing common resources setup ,
with a wiki for each business unit at my company. The common media files
would be shared and accessible by all units. Not sure yet whether there's
any requirement for a separate wiki-specific filestore for each wiki. Does
the setup mentioned in the reference allow that?