Page MenuHomePhabricator

Moving a wiki doc to the automatic location of a project page might not work properly
Closed, ResolvedPublic


I tried this once: we had a page with info on what would become a project but wasn't at the time. Then I created the project and figured I could just "move" that wiki page to the location for the project wiki page. It was allowed and worked but things were not working perfectly fine afterwards i.e. I think that wiki page was not appearing under "Projects" in the hierarchy. Moving it back did not fix the issue. I had to go in the database to fix things and manually delete some records.

That's an edge case granted, but if this is not robust, is there any reason to allow moving docs right under "Projects" in the first place?

Event Timeline

swisspol raised the priority of this task from to Needs Triage.
swisspol updated the task description. (Show Details)
swisspol added a subscriber: swisspol.

My plan is to remove the magical /projects/ directory: it predates real policies, is inflexible, and causes a lot of problems like this.

This is already mostly supported at the query layer, just not exposed in the UI (see T4029). You'll be able to make anything a "project" page by setting the policies appropriately.

chad triaged this task as Normal priority.Jun 19 2014, 4:59 AM
chad added projects: Phriction, Projects.
btrahan claimed this task.

The magical projects stuff is gone. Any legacy documents have the project policy, and then otherwise folks can create documents whereever policy allows. See T4029 for details.