This means a one-time script run won't 100% solve this.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Populate rev_content_model when a move causes default content model to change | mediawiki/core | master | +17 -0 |
Related Objects
Related Objects
- Mentioned In
- rMW0ce88ddfb2a6: Populate rev_content_model when a move causes default content model to change
T106848: Moving foo.js to foo.css works but causes "MWException: Format text/javascript is not supported" - Mentioned Here
- rMWa5bc9f49cd01: Revision: Interpret a NULL rev_content_model as the default model
Event Timeline
Comment Actions
Yep, caused by rMWa5bc9f49cd01: Revision: Interpret a NULL rev_content_model as the default model. Previously NULL meant the page's content model, which would still be set to wikitext. But now that it refers to the default, everything breaks, because page moves have the ability to change what the default model is. So, when a page is moved, we need to see if it changes the default content model, and if so update the revisions accordingly.
Comment Actions
Change 226938 had a related patch set uploaded (by Legoktm):
Populate rev_content_model when a move causes default content model to change
Comment Actions
Change 226938 merged by jenkins-bot:
Populate rev_content_model when a move causes default content model to change
Comment Actions
Talk:ET36 in testwik had page_id=969 before conversion:
MariaDB [testwiki]> select rev_id, rev_page, rev_comment, rev_user, rev_user_text, rev_timestamp, rev_content_format, rev_content_model from revision where rev_page in (969)\G
*************************** 1. row ***************************
rev_id: 2008
rev_page: 969
rev_comment: Created page with "{{#useliquidthreads:1}}"
rev_user: 285
rev_user_text: Etonkovidova
rev_timestamp: 20150730180556
rev_content_format: NULL
rev_content_model: NULL
1 row in set (0.00 sec)After conversion - page_id=978
MariaDB [testwiki]> select rev_id, rev_page, rev_comment, rev_user, rev_user_text, rev_timestamp, rev_content_format, rev_content_model from revision where rev_page=978\G
*************************** 1. row ***************************
rev_id: 2039
rev_page: 978
rev_comment: /* Taken over by Flow */
rev_user: 377
rev_user_text: Flow talk page manager
rev_timestamp: 20150731170223
rev_content_format: application/json
rev_content_model: flow-board
*************************** 2. row ***************************
rev_id: 2040
rev_page: 978
rev_comment: /* Taken over by Flow */
rev_user: 377
rev_user_text: Flow talk page manager
rev_timestamp: 20150731170224
rev_content_format: application/json
rev_content_model: flow-board
2 rows in set (0.01 sec)The page is displayed correctly.
Comment Actions
This is not regarding LiquidThreads. It's about moving (using the Move link in the drop-down menu in the tabs bar) a normal wikitext page into an occupied namespace.
For example, you could create a page in the main namespace on English Wikipedia Beta, then move it to any title in the Flow_test_talk namespace.
Comment Actions
It should remain a normal fully functioning wikitext page, despite the new namespace.