Sandbox.SomeHeader contains

%META{"parent"}%

Sandbox.SubWeb.WebLeftBar contains

%INCLUDE{Sandbox.SomeHeader}%

If you then view Sandbox.SubWeb.WebPreferences , the parent in WebLeftBar is rendered as Sandbox.WebHome instead of Sandbox.SubWeb.WebHome .

KJL

I have looked at this bug item.

First let me summarize how things work. First let us make a simpler setup.

• I have a topic Sandbox.IncludedDocument which contains %META{"parent"}% and the parent of the included topic is IncludeParent
• I have a topic Sandbox.IncludingDoc which contains an %INCLUDE{"IncludedDocument"}%. The parent of this doc is TopParent
• I have a subweb doc called Sandbox.Subweb.SubDocument which has an %INCLUDE{"Sandbox.IncludedDocument"}% and a parent called Sandbox.Subweb.SubParent

We now go through the 3 cases of wieving the 3 documents.

• When I view Sandbox.IncludedDocument the META shows IncludeParent. Just like we would expect
• When I view Sandbox.IncludingDoc the meta shows TopParent.
• When I view Sandbox.Subweb.SubDocument I see Sandbox.Subweb.SubParent

So in all 3 cases I see the parent of INCLUDING document. So there is no special bug related to subwebs here.

Now what is the spec? There is no Cairo reference to go by. The TWikiVariables topic does not specify this either. So I guess we are down to two things.

• What is the most useful behavior to to most users?
• Would there be a performance hit if we suddenly also had to read meta data from the included topics?

Personally I think the current behavior is the one that makes most sense. Why would I have a topic that includes another topic or maybe even many topics show the parent of the included topic?

It is different with variables like FORMFIELD where it is obvious that the FORMFIELD should be taking the value from the original included topic.

I think it is best to leave the behavior as it is.

I think the reporter is trying to show the parent of the current topic in the left bar.

This can be done with something like

%METASEARCH{type="parent" topic="%BASETOPIC%" format=" * $topic"}%

See the new HierarchicalNavigation topic that Arthur Clemens has recently added to the 4.1 sources. It shows how to do this.

I am discarding. Anyone that disagrees with my position is welcome to reopen and argue against. I have no strong feeling about this. I am just going through the large backlog of bugs and getting the oldest either discarded or closed with a fix.

KJL