Last modified: 2014-11-19 19:04:19 UTC
Schema Change: All wikis tables: page, revision, archive changes: Content handler columns commit status: merged MediaWiki cannot operate without these columns (fatal error). But it can be disabled with wgContentHandlerUseDB (will be in wmf-production starting 1.21wmf2) Disabled pre-emptively in CommonSettings.php --reedy Adding rev_content_format field to table revision... Adding rev_content_model field to table revision... Adding ar_content_format field to table archive... Adding ar_content_model field to table archive... Adding page_content_model field to table page... gerrit change Id4e0f40c https://meta.wikimedia.org/wiki/Wikidata/Notes/ContentHandler http://lists.wikimedia.org/pipermail/wikitech-l/2012-March/059358.html
Setting to enhancement/lowest as this is mostly a MediaWiki 2.0 thing :-)
(In reply to Greg Grossmeier from comment #1) > Setting to enhancement/lowest as this is mostly a MediaWiki 2.0 thing :-) I don't think so. Flow and MassMessage will probably want/need to start using these fields soon, so it would be nice if we could get these columns added, or at least start the process. It's been about 3 MW versions now...
Sean: Bumping priority a bit on this one because as legoktm just said on IRC: "we're going to need it for Flow at some point and the MassMessage GSoC project which will be ready by the end of the summer"
From June 11 SAL: 05:04 springle: beginning schema changes bug 49193 page_content_model
<springle> legoktm: page_content_model done, ar_content_* started, rev_content_* todo
There have been a couple of implicit and explicit requests for this, so I added bug 63885 and bug 62780. And Flow needs it to improve the way we enable Flow on a page, bug 70073. How will WMF roll out the second part (the $wgContentHandlerUseDB = true config change)? We should test on Beta labs before production (InitialiseSettings-labs.php); will we then enable all production wikis at once or start with e.g. mediawikiwiki and the wikisource wikis whose users asked for it?
$wgContentHandlerUseDB is already set to true on testwikidatawiki and wikidatawiki, so I think we can just turn it on once the schema changes are finished, no need to do it wiki by wiki,
[05:29:18] <springle> legoktm: s3 content model fields are complete That'll let us turn it on testwiki, test2wiki, and mediawikiwiki to start with.
Change 159089 had a related patch set uploaded by Legoktm: Enable $wgContentHandlerUseDB on mediawikiwiki, testwiki, & test2wiki https://gerrit.wikimedia.org/r/159089
Change 159089 merged by jenkins-bot: Enable $wgContentHandlerUseDB on mediawikiwiki, testwiki, & test2wiki https://gerrit.wikimedia.org/r/159089
Deployed by Erik, thanks!
Change 159457 had a related patch set uploaded by Spage: Set wgContentHandlerDB true for enwiki-labs https://gerrit.wikimedia.org/r/159457
Change 159457 merged by jenkins-bot: Set wgContentHandlerDB true for enwiki-labs https://gerrit.wikimedia.org/r/159457
Schema change is done on all wikis.
Change 170124 had a related patch set uploaded by Spage: Typo in labs wgContentHandlerUseDB config https://gerrit.wikimedia.org/r/170124
Change 170129 had a related patch set uploaded by Spage: $wgContentHandlerUseDB true everywhere https://gerrit.wikimedia.org/r/170129
Change 170124 merged by jenkins-bot: Typo in labs wgContentHandlerUseDB config https://gerrit.wikimedia.org/r/170124
