PmWiki | PITS / 00707

Summary: Add conditional markup to detect if text is included

Created: 2006-03-20 18:53

Status: Closed - available in 2.2.0-beta1

Category: Feature

From: Simon

Assigned:

Priority: 5

Version: 2

OS:

Description: ConditionalMarkup provides a powerful way to provide some control over the content of a page.

This proposal is to extend the conditional markup to detect if the page, or part of a page, in which the IF occurs to be able to detect when the text is included, or not.

This will provide a level of control on what is displayed on the original page, and what is displayed on the including page, over and above what can be done using (:include:).

`(:if included:)`	-	the current text is included (via (:include:), not via a template) in the page displayed.
this could be extended to detect where the include is, eg
`(:if included sidebar:)`	-	the current text is included (via (:include:), not via a template) in the sidebar of the page displayed.
`(:if included groupheader:)`	-	the current text is included (via (:include:), not via a template) in the group header page displayed.
`(:if included groupfooter:)`	-	the current text is included (via (:include:), not via a template) in the page group footer displayed.
`(:if included body:)`	-	the current text is included (via (:include:), not via a template) in the body of the page displayed. This is the default.
negated form of the condition should also work
`(:if ! included:)`	-	the current text is not included (via (:include:), not via a template) in the page displayed.
combined conditions should also work
`(:if included groupheader` `groupfooter sidebar:)`	-	the current text is not included (via (:include:), not via a template) in the specified parts of the page displayed.

This is very difficult to implement in PmWiki's current model, so it's not likely to be added soon. PmWiki doesn't keep track of the source of each markup, and nested includes pose a bit of a problem.

Would it be possible to implement a really simple part of it, eg included or not?

The new link and page-variable handling code now renders this issue obsolete.