Page MenuHomePhabricator

Eliminate $wgFlowOccupyPages and $wgFlowOccupyNamespaces
Closed, DuplicatePublic

Description

I think we just need to make sure that page_content_model is set to flow-board in the database for the pages, and $wgContentHandlerUseDB is true.

Then, I think it should Just Work, and we can take out this code.

We might also want to write a script to allow enabling a new page (depending on product decisions for enable/disable UI). It can be done with flow-create-board, but not easily for a one-off.

We can now also get rid of $wgFlowOccupyNamespaces, since now that all subpages are Flow by default there is no meaningful difference between the two.

Event Timeline

Mattflaschen-WMF updated the task description. (Show Details)
Mattflaschen-WMF raised the priority of this task from to High.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptFeb 26 2015, 11:39 PM
DannyH set Security to None.Apr 1 2015, 6:27 PM
DannyH edited a custom field.
Mattflaschen-WMF renamed this task from Eliminate $wgFlowOccupyPages to Eliminate $wgFlowOccupyPages and $wgFlowOccupyNamespaces.Jul 9 2015, 12:58 AM
Mattflaschen-WMF updated the task description. (Show Details)
Mattflaschen-WMF edited a custom field.

So, $wgFlowOccupyNamespaces will be replaced by $wgNamespaceContentModels (easy).

$wgFlowOccupyPages should be replaced by page_content_model (taken care of by T94547). Then we should run a maint. script that populates rev_content_model/ar_content_model for those pages, and then remove from config.