Page MenuHomePhabricator

Enable subpages for the Education_Program: namespace
Closed, DeclinedPublic

Description

(Filing separately from bug 45356 about the EP talk namespace, since I'm guessing this one will be less trivial to implement.)

Subpages should enabled for the Education_Program: namespace, such that a subpage of a course page behaves like a regular wiki page (editable by anyone, without any special course page elements).


Version: master
Severity: enhancement

Details

Reference
bz45357

Related Objects

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 1:22 AM
bzimport set Reference to bz45357.
bzimport added a subscriber: Unknown Object (MLST).

Er... that is indeed not trivial. And cannot be done without breaking backwards compat... or at least not easily.

EP:University of foo/Master in bar (q1/2013)

is the location for course "Master in bar (q1/2013)" in institution "University of foo". As you can see, slashes are allowed in the course name. How are you going to distinguish between a slash indicating a sub page and one part of the name? You can solve this, though then I can imagine weird situations where you cannot rename something because there is a subpage or something.

Is this really needed? Seems slightly silly to me. It'd be like creating a sub page for a wikidata item.

No, it's not really needed (although the talk namespace one would be quite helpful). It's nice to have, but not nice enough to worry much about. Feel free to close as WONTFIX.

But, is there a compelling reason to allow slashes in the titles? We don't have any on a production wiki yet, so it shouldn't be too late to disallow them. Disallowing them would avoid confusing situations with talk pages, if the talk space subpages are enabled.

You can easily have this as local config.

Disallowing them would avoid confusing situations with talk pages, if the talk

space subpages are enabled.

Well, they should not be enabled then. If they are by default, we can override this in the extension. Is that the case?

Too complicated to be worth trying to implement this in the current extension. More flexibility will need to wait until we have a more general replacement for course pages.