Item20: Plugin to make url's based on parentage rahter than web location
Priority: Normal
Current State: New
Released In:
Target Release:
Applies To: Another Product
Component:
Branches:
--
SvenDowideit - 31 Oct 2008
Tuju made me think - why are our URL's based on Web/Web/Topic? all my clients think the structure is alone topic parentage lines - so having a url that is
http://nextwiki.org/Community/CopyrightStatement/DownloadWikiBackup makes sense as Tuju points out - irrespective of
DownloadWikiBackup actually being in the Development 'web'.
<Tuju> say that i've http://host.org/Abc/Def page and I'd like to add page http://host.org/Abc/Def/Ghi - it doesn't work. Is there any way to force those urls like i want?
<Tuju> it asked me where i would like to get the page in structure, I chose to put it under Def, but page was created under Abc in URL, not under Def.
<SvenDowideit> what you're suggesting is to make twiki do nested webs automaticaly
<SvenDowideit> ie, that you created Abc web
<SvenDowideit> then made topic Def
<SvenDowideit> and then when you save a topic Abc/Def/Ghi it should make a web called Def?
<SvenDowideit> (in twiki speack..)
<Tuju> SvenDowideit the problem is, that it created http://host.org/Abc/Ghi when i wanted http://host.org/Abc/Def/Ghi
<SvenDowideit> i _think_ you _could_ write a plugin to make that happen
<SamHasler> Is there a NextWikiInTheNews topic?
<SvenDowideit> yes, it would
<SvenDowideit> as there is no Def web
<SvenDowideit> just a Def topic
<Tuju> and i could not create the Ghi at all
<SvenDowideit> the layerd nesting that twiki gies you
<Tuju> mmmm, i do know html, xhtml and CSS but these 'web' and 'topic' stuff gets me confused.
<SvenDowideit> assumes that only the last word is a topic
<SvenDowideit> and each of the other bits are webs
<SvenDowideit> web ~~ directories
<SvenDowideit> topics ~~ files
<Tuju> SvenDowideit mmm....okaaaay....
<SvenDowideit> (not just conceptually, but how they are on the disk on the server
<SvenDowideit> so ABC is a dir that gets made using Manageing Webs
<SvenDowideit> ABC/Def is a file in that web
<SvenDowideit> you can't create another file in the Def file
<SvenDowideit> you need to convince it to make a Def web
<SvenDowideit> not trivial,
<SvenDowideit> but it is possible - but will need perl code
<Tuju> okay, now i get it
<SvenDowideit> y? sweet
<carlo__> SamHasler: just what is mentioned on the homepage
<SvenDowideit> i find it painful
<Tuju> the problem is that normally apache exposes the dir+file structure as it is over http
<SvenDowideit> move that to a topic
<SvenDowideit> and use INCLUDE ;)
<SvenDowideit> Tuju, ya
<SvenDowideit> twiki doesn't
<SvenDowideit> twiki does alot of processing
<Tuju> and makes index files as pages in dirs
<SvenDowideit> yup
<SvenDowideit> twiki's 'index' files are the WebHoe topics
<carlo__> SamHasler: but no NextWikiInTheNews topic
<SvenDowideit> WebHome..
<SamHasler> carlo__, thx
<Tuju> so, what i would need, is to change the Abc/Def to dir, but also make is visible as a page.
<SvenDowideit> ish
<SvenDowideit> in twiki you can create a Def web using ManageingWebs
<Tuju> and then it makes me to think that TWiki has a limitation in url component depth
<SvenDowideit> then there will be _some_ confusion between the Def topic and the Def web
<SvenDowideit> in a way yes
<SvenDowideit> it does a thing called nested webs
<SvenDowideit> but they are created by admins
<SvenDowideit> if you have time and patience
<Tuju> so i could change Def as webhome and get what i need if i'm lucky? :)
<SvenDowideit> I could make a plan for how to make the url's work on BreadCrumb path
<Tuju> SvenDowideit ouh, time and patience is just what i don't have
<SvenDowideit> i thought so :)
<SvenDowideit> Tuju, bingo
<SvenDowideit> make Def web
<SvenDowideit> then move the Def topic content to the Def web's WebHome
<Tuju> kind of got disapointed that wiki turned out to be this complex
<SvenDowideit> you've groked it right
* ArthurClemens (n=arthur@natpool-1.lostboys.nl) has joined #twiki_fork
<Tuju> SvenDowideit i'll try that now
<SvenDowideit> manyway nestig is not something that alot of wiki users have desired
<SvenDowideit> but you've made me thing of some really cool magic
<SvenDowideit> register on nextwiki.org, and you might be able to help us make it do what you have in mind :)
<Tuju> SvenDowideit i'll think about that
<SamHasler> Tom Barton also posted his response from RelaunchTWikiOrgProject on slashdot: http://tech.slashdot.org/comments.pl?sid=1011659&cid=25574345
<SvenDowideit> :)
<SvenDowideit> oh, what a good man
<SvenDowideit> can't edit that away later
* gmc clicks '-'
<Tuju> i'm still wondering and trying to explain myself why i should try to learn n dialect of wiki, once i already master xhtml+css :)
<gmc> :)
<SvenDowideit> Tuju, hehe
<gmc> Tuju: you can just use html in twiki topics.. if you skip the wysiwyg
<SvenDowideit> one reason - its an application platform
<gmc> xhtml
<gmc> but it tends to get overly verbose..
<Tuju> and being a wikipedia author for some documents, it has quite many times turned out to be equally complex but also more limiting than plain xhtml.
<SvenDowideit> yup
<SvenDowideit> nextwiki's closer to php than html
<Tuju> wiki has somewhat easier ways to express tables for example, but some easier areas are still quite heafty price tag for the learning curve and trouble for completely new system.
* vmlemon_ has quit (Nick collision from services.)
<Tuju> gmc yes, i can and have used it in trac wiki for example. but the i ask - why i should do editing in unreliable TEXTAREA+unstableHTTPconnectio when i could do it in my favorite editor and some SCM client? :)
<gmc> tbh, i sin sometimes and just vim a twiki topic at the back end :)
<Tuju> gmc well, you're not far from making it over subversion/git/cvs whatever and create triggers into server end to expose the HEAD wdir into apache, right?
--
SvenDowideit - 31 Oct 2008
to add to this, I recon We could implement this as a plugin now.
--
SvenDowideit - 31 Oct 2008