Store Web in TOPICPARENT meta
We should always be storing the Web in TOPICPARENT meta.
Right now it supports both
web.topic
or
topic
format.
IMHO TOPICPARENT should always store the unique ID of the parent i.e.
web.topic
even though we want to
AvoidParentAcrossWebs.
The current situation just make it harder for plug-in developer. More over it should also help us to implement things like
GetRidOfTheDot.
--
Contributors: StephaneLenclud - 06 Apr 2007
Discussion
I concur.
--
SvenDowideit - 06 Apr 2007
Where in the code is this handled differently? It sounds strange if sometimes it is with web and sometimes without.
--
KennethLavrsen - 07 Apr 2007
It probably always use only
topic
in the parent property handling code. Then when you move topics from one web to another one links get updated include parent link I suppose. That's where
web.topic
start to show up in the meta. That's Just a guess. The parent property handling code itself should use
web.topic
in the first place.
--
StephaneLenclud - 07 Apr 2007
See
Bugs:Item4417. In
NatSkin it's the responsibility of the
edit.nat.tmpl
to store
TOPICPARENT
as
web.topic
. I assume another template is responsible for doing the same on
PatternSkin.
--
StephaneLenclud - 31 Jul 2007
Please raise a bug against
PatternSkin.
NatSkin is not in the release, and unless there is an urgent bug against
PatternSkin it won't get fixed in 4.2
--
CrawfordCurrie - 31 Jul 2007
No, there is a big drawback of the name of the web is duplicated in the TOPICPARENT: Now it is possible to simple rename a web on the shell level, or migrate to a different TWiki with different web name (company mergers etc) and it "just works." We have a problem if we duplicate the web name in TOPICPARENT, it is already implicitely in the name of the current web.
The only reason to store web.topic in TOPICPARENT is to link a parent across webs, which is a bad idea from a usability perspective (don't make me think.)
--
PeterThoeny - 01 Aug 2007