Item5404: Breadcrumbs do not properly map to subwebs
Priority: Normal
Current State: Confirmed
Released In: n/a
Target Release: n/a
Applies To: Engine
Component:
Branches:
Breadcrumbs show Foo/Bar for subwebs, rather than Foo > Bar. Unfortunately, this means that the web and subweb cannot be clicked independently in the breadcrumbs path.
For example, we have a web: Projects, with a subweb: DT_Logger
The breadcrumbs allow me to reach Projects/DT_Logger.WebHome but
not to reach Projects.WebHome
--
TWiki:Main/VickiBrown - 01 Mar 2008
- screen shot of example:
Try
TWiki:Plugins/BreadCrumbsPlugin
--
MichaelDaum - 01 Mar 2008
Plugin or not, this should get fixed.
--
ArthurClemens - 01 Mar 2008
Affects the core too. Confirmed.
--
CrawfordCurrie - 27 Jun 2010
The bug is still there. You still get a bredcrumb that does not give links to the individual webs.
If you have a topic web Rootweb/Middleweb/Bottomweb/Bottomtopic then the breadcrumb shows "Foswiki > Rootweb/Middleweb/Bottomweb > Bottomtopic" which is ONE long link to Rootweb/Middleweb/Bottomweb/WebHome. What Vicki wanted and other have confirmed is that Rootweb, Middleweb, and Bottomweb should link to the WebHomes of the parent webs.
But the solution is not obvious.
Let me give some examples.
Topic |
Parent |
Desired breadcrumb |
Obvious? |
Rootweb1/Mediumweb1/Deepweb1/Mytopic |
Rootweb1/Mediumweb1/Deepweb1/Myparenttopic |
Rootweb1/Mediumweb1/Deepweb1/Myparenttopic/Mytopic |
Yes |
Rootweb1/Mediumweb1/Deepweb1/Mytopic |
Rootweb1/Myparenttopic |
Rootweb1/Myparenttopic/Mytopic or Rootweb1/Mediumweb1/Deepweb1/Myparenttopic/Mytopic |
No |
Rootweb1/Mediumweb1/Deepweb1/Mytopic |
Rootweb2/Mediumweb2/Deepweb2/Myparenttopic |
Rootweb2/Mediumweb2/Deepweb2/Myparenttopic/Mytopic or Rootweb1/Mediumweb1/Deepweb1/Myparenttopic/Mytopic |
No |
Rootweb1/Mediumweb1/Deepweb1/Mytopic |
Rootweb2/Myparenttopic |
Rootweb2/Myparenttopic/Mytopic or Rootweb1/Mediumweb1/Deepweb1/Myparenttopic/Mytopic |
No |
You can argue that the breadcrumb should show the web path of the current topic.
Or you can argue that the breadcrumb should follow the parents until there are no more parents and then from there follow the web path back. I believe this how it works now.
I am personally most in favior of the current approach. But I perfectly understand the arguments for the other. And making it configurable is a bad idea. Things should always work the same way.
But in both solutions. Or all 3 because there may be a 3rd solution. In all solutions, the original bug report asked for the webpath to be split in individual parts so you can navigate up one web level via the breadcrumb. Today you can only go to the
WebHome of the web of the most senior parent topic or all the way to the root web. You cannot get to the middle web levels.
--
KennethLavrsen - 09 Nov 2010
would it make sense to still follow the Parent / Child topics delimited by the ">" but make the individual web components clickable as well.
Rootweb1/
MyParentTopic >
Rootweb1/
Mediumweb1/
MyTopic
So clicking the topic name takes you to the topic, but clicking any of the web components takes you to the webhome of that particular web? Or would this end up being too confusing?
--
GeorgeClark - 09 Nov 2010