For example, I wound up with:

CSA > TWiki.TWikiTipsOfTheDay > TWikiTip001

This may be true in 4.0.x as well.

Right..... so what's wrong with that? It seems pretty intuitive to me....

CC

I guess I assumed that a topic's parent would always been in the same web. If that's not the case, then this isn't a bug, but it's quite disconcerting to click on the breadcrumb and suddenly be in a different web which may look quite different.

ML

It's not the case. The breadcrumb looks ok once you get used to it.

CC

I disagree. It breaks the mental navigation model. Don't make me think

The correct fix is to remove the parent if the topics is moved from one web to another.

-- PTh

Quite on the contrary, I've always experienced it as a nasty restriction that I can not (re)parent a topic across webs. Webs are, per technical definition, server-side organisation issues (e.g. with regard to access control), whereas the breadcrumb/parent structure can be driven content-oriented. Example: A topic like TWiki:Codev.TransparentAuthentication would have a "natural" parent in TWiki:TWiki.TWikiUserAuthentication, rather than in TWiki:Codev.WebHome or in "no parent at all".

I concede that the feature to create cross-web breadcrumbs by moving topics is rather coincidental, in the sense of "the current implementation turns out to behave like that". Removing the parent makes the behaviour consistent, but, in my opinion, consistently deficient.

-- TWiki:Main.HaraldJoerg

I have to (mostly) agree with PTh here. There should at least been an option to remove the parent. For me it's not a "Don't make me think" item so much as a) it creates an extra step in authoring to fix up the parent and b) as I said above, it can be disconcerting to click a topic's parent and wind up in a different web that looks quite different.

There's also a bug in patternskin, last I looked, with this. I'll have to investigate a bit before posting a bug report.

ML

Moved to TWiki:Codev.PoorLittleOrphans and discarded, as this is a case of something needing user discussion and not a bug per se.

CC