Last modified: 2014-09-19 02:56:22 UTC
When running update.php during an upgrade, the following error occurs: A database error has occurred. Did you forget to run maintenance/update.php after upgrading? See: https://www.mediawiki.org/wiki/Manual:Upgrading#Run_the_update_script Query: SELECT page_id,page_len,page_is_redirect,page_latest,page_content_model FROM `page` WHERE page_namespace = '10' AND page_title = 'Extension_DPL' LIMIT 1 Function: LinkCache::addLinkObj Error: 1054 Unknown column 'page_content_model' in 'field list' (ipaddr/socket here) I'm currently upgrading from 1.20.8 to 1.23.2 but I've seen this for quite some time and there has been previous discussion around it. See for example: http://www.mediawiki.org/wiki/Thread:Project:Support_desk/upgrade_from_1.16.1_to_1.21.1_failing The workaround I'd been using was to comment out DPL for the script run (which apparently doesn't work for everyone), but this adds unnecessary downtime to the upgrades. Vulpix on IRX suggested the update.php script should be creating the relevant fields (i.e. page_content_model) and that I submit a bug, so here it is.
"DPL" = https://www.mediawiki.org/wiki/Extension:DynamicPageList_%28Wikimedia%29 ?
Sorry I wasn't clear. It's the third-party DPL. http://www.mediawiki.org/wiki/Extension:DynamicPageList_(third-party) However, it's not clear if DPL is the issue or if it's just the thing showing the error. That's what the thread I linked seemed to imply, but commenting out DPL did work for my environment. Hence the question mark in the bug title. :) For what it's worth, setting $wgContentHandlerUseDB to false for the duration of the update.php script also worked for me.
Moving component. DPL appears to be at fault, not the core upgrade script. (At least I'm blaming it)
Hmm, its a dupe. And there's a patch in core apparently. But not backported I guess. *** This bug has been marked as a duplicate of bug 60492 ***