2011/5/16 Tanguy Ortolo <tanguy+dokuwiki@xxxxxxxxx>: > Andreas Haerter, 2011-05-16 19:41 UTC+0200: >> For sure... but you just have to decide for one behaviour: >> a) let existing files win >> b) let DokuWiki win in every case = current behaviour >> >> Everything in between can't be completely automatic or you really need a >> namespace for the wiki. > > Yes indeed, this is what I suggest. This is not only my idea: it is > systematic with MediaWiki for instance. > >> A namespace also just moves the problem because you have to hope that >> you will never have to create a page outside this namespace then. And I >> think the probability that a user would like to use >> <http://example.com/foobar> outside <http://example.com/wiki/*> for his >> wiki is much higher than inaccessibility of a clearly defined blacklist >> (=existing files and dirs). > > Okay, I reckon I may have not been clear enough. When I speak of a > namespace, I do not mean <http://www.dokuwiki.org/namespaces>: I am > refering to a web path. > > I am suggesting to allow DokuWiki to serve all its pages, regardless of > their namespaces, under some path one level under its own root path, for > instance <http://wiki.example.com/pages/*>, instead of > <http://wiki.example.com/*>. Thus, a page such as namespace:pagename > would be server under <http://wiki.example.com/pages/namespace:pagename> > (or perhaps <http://wiki.example.com/pages/namespace/pagename>). it's already possible to not install dokuwiki in/as the root of a website, producing this web path you speak of. -- DokuWiki mailing list - more info at http://www.dokuwiki.org/mailinglist