Edgewall Software

Opened 16 years ago

Last modified 7 years ago

#3021 new enhancement

wiki namespace support like the one in dokuwiki — at Version 8

Reported by: trac.ticket@… Owned by: Christian Boos
Priority: high Milestone: next-major-releases
Component: wiki system Version: none
Severity: major Keywords: wiki namespace structure
Cc: itamarost@… Branch:
Release Notes:
API Changes:
Internal Changes:

Description (last modified by Christian Boos)

It would be very great to have wiki namespace support, for sorting wiki pages and protect user to build too big pages. I think it's very important to support wiki namespaces.


As the topic is broad, it's worth to discuss it in a specific proposal page, see TracDev/Proposals/WikiNamespaces.

Change History (8)

comment:1 by Christian Boos, 16 years ago

Description: modified (diff)
Milestone: 0.10
Priority: normallow
Severity: normalminor
Summary: wiki namespace support like the one in docuwikiwiki namespace support like the one in dokuwiki

We already support scoped WikiPageNames, but I guess we could improve a bit the readability of those names.

If we're in a page belonging to a given "namespace", that leading prefix could be omitted when displaying references to other pages sharing the same namespace.

E.g. in the page TracDev/DatabaseSchema a reference to TracDev/DatabaseUpgrades would read DatabaseUpgrades (it would still have to be written in full, though).

This would be useful if we move all Trac documentation pages in TracGuide/<something> or TracHelp/<something>, as it's sometimes requested.

comment:2 by christian.aust@…, 15 years ago

Priority: lownormal

I'd like to vote for this, too. Having proper namespace support would indeed help to clean up some wiki issues. Real namespaces would also allow to narrow a search down to certain sets of pages, which is nice if you share one instance of trac for different projects.

I'd like to see this in future versions. Just my $.02.

comment:3 by anonymous, 15 years ago

what is the difference between this "subwikis" like TracDev/… and a namespace?

you mean to extend search to just search "TracDev" and nothing else?

comment:4 by Christian Boos, 15 years ago

Resolution: duplicate
Status: newclosed

The ...:WikiPageName syntax is already used for InterWiki and InterTrac links. It's not impossible that in the future, when there's support for Multiple Projects (#130), the use of InterTrac prefixes to specify some other projects will actually achieve a result quite close to what was requested here.

But for now, Trac support scopes by the way of scoped WikiPageNames (CamelCase words separated by "/"). The support for this can certainly be enhanced (see #4507). Introducing a different syntax (the DokuWiki one) would not bring any advantage over this, and, as explained before, will conflict with Inter(Wiki/Trac) links.

in reply to:  4 comment:5 by Christian Boos, 11 years ago

Milestone: next-major-0.1X
Owner: changed from Jonas Borgström to Christian Boos
Priority: normalhigh
Severity: minormajor

Reconsidering comment:4:

The ...:WikiPageName syntax is already used for InterWiki and InterTrac links. It's not impossible that in the future, when there's support for Multiple Projects (#130), the use of InterTrac prefixes to specify some other projects will actually achieve a result quite close to what was requested here. … Introducing a different syntax (the DokuWiki one) would not bring any advantage over this, and, as explained before, will conflict with Inter(Wiki/Trac) links.

The advantage of namespaces over the hierarchy would be the possibility to assign a special semantic to set of pages, a kind of specialization of wiki pages. For example Help: for Trac's own help pages (#3386), Template: (for transclusion support a la MediaWiki), Category: for tagging, Special: for special pages like BadContent, TitleIndex, InterMapTxt, …

The hierarchy is there to structure the content in the main namespace (wiki:), like here TracDev/CookBook/… and the namespaces could be used for segregating special wiki pages which are not to be considered part of the content.

comment:6 by Christian Boos, 11 years ago

Resolution: duplicate
Status: closedreopened

comment:7 by Itamar Ostricher, 11 years ago

Cc: itamarost@… added

comment:8 by Christian Boos, 11 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.