PmWiki | PITS / 00779

Summary: (:title:) directives should not have effect in (:include:) included pages

Created: 2006-07-28 08:24

Status: Open

Category: Bug

From: Roman JamesM Mike

Assigned:

Priority: 554

Version: 2.1.11

OS: Win/Apache/4.4

Description: Announced as being fixed in 2.1.6 (http://article.gmane.org/gmane.comp.web.wiki.pmwiki.user/26922/match=include+title+directives+don+t+mix) but problem still persists.

Was called 'not a bug' in PITS.00266 JamesM
Consider this use case FOR blocking included title directives.
1. A page called 'mynavigator' with a list of pages and a :Title The Big Navigator: directive.
2. An :include mynavigator: on a number of pages that are using the navigator
3. Now all pages would have the same title, The Big Navigator, for any tools that respect thier renamed title when listing them!
In fact, much as you use $= $* and $ to give context to variables, some directives may need to have specific contexts

Suggestion:

Title is a form of page-specific metadata. There should be a metadatablock at the beginning of a page where you can assign arbitrary key=value pairs that can be used by other tools. These are locked to and evaluated in the page context, even if the page is included in another scope.

So perhaps if a final page has two consecutive titles, the second one is being used instead of the first. Perhaps this could be reversed and even a variable added to specify whether the first or last metadata have priority on a page.

Solution by using recipe TitleMarkup as an alternative title markup which will display first title. HansB April 03, 2008, at 10:32 AM