Jun 11 2018
Aug 17 2017
Rename tables mwuser to user, and pagecontent to text. Table names are always quoted, so
it doesn't matter if they are keywords. A table prefix can be used if desired to avoid having
table names that are keywords.
Not sure how I missed this task until now. I'm mostly okay with this, but the timestamp change in particular seems a step in the wrong direction.
Aug 9 2017
A good extension name, that explains intuitively what it does and avoids generic words
Oct 16 2016
Ok, well it was just a quick idea. If I get some time I will test this out but most of my test boxes cannot handle 1.28 at the moment due to the recent PHP requirement.
What about simply changing the $conn->query("createdb") to $conn->doQuery in PostgresInstaller.php? We lose some random sanity checks and profiling, but this is a one-time create database call so those are not really important.
Sep 28 2016
This extension is at mediawiki.org as EmailDiff
Sep 6 2016
A basic first step for questions like this is to see what the major distros (especially the LTS ones) are providing for node versions. As a point of data, looks like CentOS 7 is providing 0.10.46. On the other hand, we usually end up installing a local node anyway, so it won't affect us very much.
Mar 24 2016
As a heavy "third-party MediaWiki operator", I am fine with requiring mbstring. It's standard, in all packaging systems, easy to enable, and seems a low cost for a high payoff.
Mar 13 2016
Feb 22 2016
FWIW, this is now a full-blown extension:
Jan 31 2016
Jan 6 2016
Are there any temporary workarounds? Willing to monkeypatch as heavy as needed....
Dec 3 2015
"If one other person (any pre-existing Phabricator user) wants to put their name down as being unequivocally opposed to releasing 1.27.0 with a PHP 5.5 requirement" Barring better arguments for 5.5 than "has some neat stuff we would like to maybe use", and as someone who has hacked production code to get MW installed on machines with a too-low-but-still-works PHP versions :), I'm opposed for now.
Nov 12 2015
Time for a new release!
Looks like this was fixed in acd40b8fa82c04e80d390f650ee368bbdd4628cd
Oct 29 2015
Worked around this with a cronjob executing runJobs and turning off all async calls, but this is a very nasty bug.