I administer a public wiki - https://wiki.seg.org - and I am having issues
with a jobs backlog. It's currently at 19,058 and counting. I have tried
using runJobs.php, but I get this error message:
PHP Fatal error: Allowed memory size of 157286400 bytes exhausted (tried to
allocate 3846541 bytes) in
/var/www/html/mediawiki/includes/objectcache/SqlBagOStuff.php on line 656
I have noticed I do not have the variable:
$wgJobRunRate
listed in my LocalSettings.php.
Should I add this variable to my LocalSettings.php file? How can I address
this error message? I believe the jobs backlog is contributing to a
Translate extension error I am having, mentioned here -
https://phabricator.wikimedia.org/T159947.
I am running MediaWiki 1.26.2. The jobs back log started in November 2017.
No changes have been made to my version of Mediawiki in that timeframe.
Thank you.
Best,
Andrew
Andrew Geary | publications outreach editor
+1.918.497.4615 | ageary(a)seg.org
Society of Exploration Geophysicists (SEG)
8801 South Yale Ave, Ste. 500, Tulsa, OK 74137 USA
I worked on the Lingo extension ([1]) in the past few days, fixing bugs and restructuring the injected HTML to be less intrusive in the main article text. In the past there were reports about incompatibilities with other extensions and the latest changes should potentially fix some of these issues.
There are currently 4 specific tasks on Phabricator related to incompatibilities with other extensions:
* https://phabricator.wikimedia.org/T123966 (SpamBlacklist)
* https://phabricator.wikimedia.org/T123962 (MobileFrontend)
* https://phabricator.wikimedia.org/T123968 (Visual Editor)
* https://phabricator.wikimedia.org/T123971 (Page Schemas)
My problem is, that I do not use these extensions and don't know much about them, so I would be really grateful if somebody else could do some testing together with the latest dev version of Lingo and give me feedback.
Cheers
Stephan
[1] https://www.mediawiki.org/wiki/Extension:Lingo
Hello everyone,
We are releasing the next version of the Parsoid deb and npm packages
(v0.9.0) later today. There is one significant change in this release
that might affect some VisualEditor installations. This version of
Parsoid wraps sections in <section> tags and bumps the HTML version to
1.6.1. However, VisualEditor installations older than Dec 12, 2017 are
not compatible with this section wrapped output.
In order to prevent silent failures, Parsoid will do a hard fail and
reject parse requests with a HTTP 406 when it receives a version string
smaller than 1.6.0 (which VE before Dec 12, 2017 would issue). VE will
then popup the following error: "Error loading data from server:
apierror-visualeditor-docserver-http: HTTP 406. Would you like to
retry?" Retries won't help in this scenario.
Knowing this, you have a couple of options:
* Not upgrade Parsoid. If you upgrade Parsoid without reading this
notice and later stumble on this (which we'll also add to the
Parsoid releases page), you have the option of downgrading your
Parsoid install by downloading an older deb package from
https://people.wikimedia.org/~ssastry/parsoid/debs/
* If you choose to upgrade Parsoid and your VE installation is from
before Dec 12, 2017 (which is probably most of you), the recommended
solution is to upgrade your VisualEditor installation as well.
If for some reason you really really need to upgrade Parsoid but cannot
upgrade VisualEditor, contact us on IRC in #mediawiki-parsoid to ask us
how you can do that.
Subbu.
(on behalf of Parsoid developers).
I would like the signature button in the enhanced editing toolbar to add
the signature as "~~~~" and not as "--~~~~". So I have a script in my
person JS which is shown below. But it does not actually work, i.e. the
signature button still adds the --. I think it is because the JS below is
not run *after* the button is set up, but rather before it is set up. What
dependency should I add so that this script is executed after the buttons
in the enhanced editing toolbar are loaded?
Thanks in advance,
Huji
// no -- prefix for signature
buttonmw.loader.using(['mediawiki.util'], function() {
$("a[rel=signature]").unbind("click").click(function()
{insertTags('~~' + '~~')});});
Hi everyone,
The 4th episode of the MediaWiki podcast "Between the Brackets" has been
released, featuring an interview with longtime MediaWiki user Bernhard
Krabina, who works for the Austrian e-government organization KDZ. You can
listen to it here:
http://betweenthebrackets.libsyn.com/episode-4-bernhard-krabina
-Yaron
Although MediaWiki 1.26.x family is older, we are still using it right now.
I would like to use an extension that is no longer available on the distributor because of
the version 1.26.x. Is there any way to get the older extension ?
thanks !
Lori
> I wonder what the general reaction would be to a men only hackathon ?
Probably disbelief followed by ridicule since this is 2018 and we’re still hearing preposterous arguments like this one.
Yours,
Chris K.
*Dear sir, madamWikimedia Nederland is organizing her very first Women Tech
Storm.This event is a small female-only hackathon. It is also open for
non-binary people. It will be held in The Hague from 10-12 May 2018.It will
be an extended weekend filled with hacking together with other interested
developers. The Hackathon has two targeted groups. One group exists of
female developers with some experience programming outside Wikimedia and
who would like to learn Wikimedia coding. The other group consists of women
who are already acquainted with Wikimedia projects and are interested in
learning the coding side of the projects. You can learn how to make a query
with SPARQL or learn to master Python.The Women Tech Storm - part I will be
followed by Part II. This event will be in October/November and is open for
all genders.Participation is free of charge and it includes entrance, meals
and hotel: we ask of people participating to join us in Part II.Please see
the registration form
<https://docs.google.com/forms/d/e/1FAIpQLSfxaMsbZGyaM42zunpdEHpeD6knSzpBsZP…>
or our page on mediawiki.org
<https://www.mediawiki.org/wiki/Netherlands_Hackathon_2018_-_Women_Tech_Storm>
for more information. If you have any questions, please email to
Hackathon(a)wikimedia.nl <Hackathon(a)wikimedia.nl>*
On behalf of the work group,
Kind regards,
Michelle Boon
Event Organiser & Community Support
Wikimedia Nederland
(ma, di, do*)*
*Bezoekadres:*
Mariaplaats 3
Utrecht
*Wikimedia Nederland organiseert regelmatig bijeenkomsten, u bent daarbij
van harte welkom. Kijk voor meer informatie in onze agenda
<https://www.wikimedia.nl/pagina/agenda>.*
Hi Guys,
We have been running Private MediaWiki with VisualEditor and using
Parsoid provided by a Heroku instance for some time and this has worked
with out an issue.
We recently needed to move our Wiki to a new host and change the hosting
URL (this part may be important).
So I updated my $wgServer & $wgScriptPath with the new domain and path.
I then spun up a new Heroku Instance for this new url. I also updated
the $wgVirtualRestConfig url for the new Heroku App.
Now when testing and attempting to edit a page checking the log on
Heroku I receive the following error: "Your wiki requires a logged-in
account to access the API."
If I make the wiki public readable the editor,
change $wgGroupPermissions['*']['read'] = false;
to $wgGroupPermissions['*']['read'] = true; the editor works fine.
The only thing that has changed as mentioned is we have moved to a new
host and we moved from a subdomain to a folder.
So we have gone from wiki.example.net to www.example.net/wiki.
Any help you can give would be appreciated.
Thanks.
Matthew