First of all, thanks for choosing the Cargo extension! As the main author
of that extension, I'm happy you're trying it out.
So, by an amazing coincidence, over the last month or so I've been working
on creating a new extension that allows for saving and displaying BPMN
diagrams within the wiki. The extension isn't released yet, and it doesn't
even have an official name yet - right now it's called "Diagrams",
because it's meant to support other diagram languages besides BPMN,
although right now it only supports BPMN.
However, you can already see it in action on this wiki:
The contents of that wiki page are simply one BPMN file - it's an approach
similar to what the Scribunto extension does with Lua modules. To edit the
diagram, you can edit the text directly, or click on the "Edit diagram" tab
to edit it graphically, using bpmn.io:
There's even a Cargo tie-in - some of the essential information from all
the diagrams is stored in a Cargo table, where it can be queried:
It's a somewhat different approach from what you are trying to do, but
hopefully similar enough that it would be useful for you.
I'm curious to know what you think - if you want to talk about it further,
please write me back, privately or on this mailing list.
On Tue, Sep 16, 2019 at 6:38 AM Alain PERRY <alainp(a)franceactive.org> wrote:
> Hello list,
> I was sent here from the #mediawiki IRC channel, I hope this is indeed the
> correct list to write to and ask you to please forgive me if it is not.
> First, a bit about myself: I'm no real developer, just a tech-savvy guy
> trying to build a wiki to document my employer's company inner workings.
> This last bit means documenting any piece of information we handle and our
> business processes in doing so.
> After testing a few wiki engines, I came to the conclusion that mediawiki
> with the cargo extension was what I was looking for. I also built a small
> extension to allow inclusion and edition of BPMN diagrams with the
> https://bpmn.io library. All in all, this is pretty basic.
> Then I came to the realization that if I wanted any lambda-user to be
> willing to contribute to the wiki content, I needed the Visual Editor.
> Deploying it was easy enough, and everything seems to be working fine at
> the moment.
> I however feel I should make it possible to include a BPMN diagram from
> the VE toolbar. Ideally, this will take the form of a "popup" that will
> include the bpmn.io modeler to edit the diagram. However, in order to
> achieve this goal, I have a whole damn lot to learn and to experiment with
> about VE.
> So I thought I should start with something a little humbler: a button that
> would just include some basic XML in the page (a special page already
> allows editing that part of the page, so this would already be convenient,
> though far from perfect). Using the gadgets example from the documentation
> on the mediawiki wiki, I'm able to insert content into the page. But that
> content is escaped if it includes XML and I have no idea from the API doc
> how to include something less basic than mere text (or than a given
> template, since the example actually shows how to do that).
> What I'm actually getting at is this: would someone with good knowledge of
> the API and some good old patience be willing to "tutor" me by giving
> pointers where I need them ?
> My first technical question would be this: I understand that my gadget can
> register a ve.ui.Command, that will in turn call a method on an
> ve.ui.Action object. I guess I should stick to the ContentAction one. But
> I'm not sure what the "content" parameter should contain if given an array.
> Is there, somewhere, some documentation I can read on this?
> Thanks a bunch for any help.
> Alain Perry
WikiWorks · MediaWiki Consulting · http://wikiworks.com
We are beginning the process of working on the 1.34.0 release of MediaWiki.
The release is currently scheduled for November 2019.
We anticipate creating the REL1_34 branch on September 30 (aligned with the
final Wikimedia alpha 1.34.0-wmf.25), so we are asking for "pencils down"
on September 29. Once the REL1_34 branch is cut, any patches that need to
get into the release will be in the normal patch master + backport process
until the release in November.
If you have any open Phabricator tasks tagged with mw-1.34-release ,
please check to see if they are indeed blockers for the release. If not,
please remove the tag from them. Conversely, if there are any blockers that
are not tagged with mw-1.34.release, please tag them.
Please feel free to reach out to me if you have any questions about this.
Product Manager, MediaWiki Platform
PolyGerrit no longer supports Internet Explorer. It never really worked so now the offical status is "not supported".
You can use alternative browsers like Chrome, Firefox, Opera and Microsft Edge.
GWTUI will support internet explorer. Though GWTUI has been removed in newer versions of gerrit.
Deployment of MediaWiki 1.34.0-wmf.22 on the Wikimedia cluster is
currently blocked. It is blocked on a php7.2 bug that has yet to be
tracked and determined.
Immediately after deploying to group1 (which has commons and wikidata),
I noticed an infamous error in the logs:
PHP Notice: Undefined index:"
Which sounds similar to known errors with php7.2 (T229433, T231089 among
others) but this time it hits LBFactoryMulti.php which is for the
database load balancing. So that sounds scary and I thus decided to
block the train.
The notice happens at:
The GROUP_GENERIC constant is an empty string. Brad "anomie" Jorsch
quickly found out the code always set that key!
So what is left is a edge case issue in php 7.2, maybe in the opcache or
something even scarier.
Thanks to Tim Starling, we have a solution to issue a core dump of php
when that issue happens. There is already available on the cluster, but
it has to be investigated which is not that trivial.
We have started using the wikimedia-android-data-client library(
https://github.com/wikimedia/wikimedia-android-data-client) to make
mediawiki api calls in the Commons Android app, replacing the legacy
library that we were using previously. Most of the authenticated calls
(i.e. login, upload, nomination for deletion, thank, notifications etc)
made to Commons wiki are working with the new library, but we are stuck
with a cross-wiki call to Wikidata. We are trying to call
`Service:wbcreateclaim` to create a claim on Wikidata but the call is
We have posted relevant http logs at
We would greatly appreciate it if could take a look at the logs and suggest
what we might be doing wrong. Is it because of some issue with cookies?
Because as far as we can see, as expected we are sending the params in POST
request body with application/x-www-form-urlencoded.
Relevant method call: service.postCreateClaim(entityId, snaktype, property,
value, "en", csrfTokenClient getTokenBlocking())
Thank you so much!
Discussion in https://phabricator.wikimedia.org/T232224. I had trouble
connecting to Phabricator also, so I'm guessing that IRC is a good
alternate channel for communications. However, as usual, let's not all pile
into IRC, email, and/or Phabricator and say "I'm having problems connecting
to Wikimedia sites" when the technical ops folks are working on this.
( https://meta.wikimedia.org/wiki/User:Pine )