authors (intermediate)
The SyntaxThe basic syntax is with pagename includes the full page from the same group.
The full syntax is includes a page according to the parameters supplied. Parameters are optional.
ParametersThe directive can have multiple Name parameters with or without anchors, and multiple template variable parameters. Named pages(:include PageName:)
(:include Group.PageName:)
(:include Page1 Page2 Group1.Page3 Group2.Page4:)
Includes the entire text of another page into the current page. Multiple pages may be specified, but only the first available is included.
You can use the above feature to display an error message if an include fails. Create a page, eg. Site.Include Failed? containing the error message. You can use any page name. Then, in your include markup, append this page at the end of the page list: (:include Page1 Page2 Page3 Site.IncludeFailed:) A slightly more complex approach is outlined at the talk page. #From#To anchors
Note: do not put whitespace between “#from” “#to”
Note: text on the same line as a closing anchor but preceding the closing anchor will NOT be included in the text. Example Below:
[[#start]]some text on the first line
some text on the last line [[#end]]
The above, when included via (:include PageName#start:) will have the text on the first line but not the text on the last line.
(:include Page1 Page2 #from#to:)
Include from the first available of Page1, Page2 between the [[#from]] and [[#to]]
Note: put whitespace between “Page2” and “#from#to”. The same anchors “#from#to” should be in both pages. If proper anchors are missing in the first available of Page1, Page2 the whole contents of the page is included.
This does not seem to work in 2.2 betas. See Cookbook:IncludeSection for a fix.
(:include Page1#from1#to1 Page2#from2#to2:)
Include the first from the first available of Page1 (between the [[#from1]] and [[#to1]] ) or Page2 (between the [[#from2]] and [[#to2]] )
Note: Previous versions of PmWiki allowed whitespace between #from and #to anchors even though it was not designed to. Newer versions do not allow whitespace anymore. To re-enable this “exploited misbehavior” put this into your config.php or farmconfig.php
Markup('includeanchors', '<include', '/(\\(:include.*?#\\w+)\\s+(#\\w+)/', '$1$2');
Lines=from..to(:include PageName lines=10:)
(:include PageName lines=5..10:)
(:include PageName lines=5..:)
Include the first 10 lines, lines 5–10, or lines 5 and up from PageName. A “line” in this context refers to a line of source. Thus a line may be a paragraph that wraps over several lines on the screen, or a completely blank line.
(:include Page1 Page2 Page3 lines=1..5:)
Include the first five lines from the first available of Page1, Page2, or Page3. (To include lines from a list of pages, use a separate include for each.)
Self=(:include PageName self=0:)
The parameter self can be 0 or 1 . It tells the include directive if it is allowed to include the current page. This is useful if Page Name? is a variable like {$Name} and you want to prevent the directive from including the current page.
Page text variables{Group/PageName$:Var}
Includes definition list values from an (optional) page as page text variables. These are defined using a definition list ( :item:description ), simple colon delimiter (item:description ), or special markup ((:item:description:) ).
Basepage=(:include PageName basepage=BasePageName:)
Include Page Name?, but treat all relative links and page variables on Page Name?` as relative to Base Page Name?.
If Name: {$:Name} Address: {$:Address} then the directive (:include TemplateName basepage=PageName:)
will retrieve the contents of Basepage usageThe primary purpose of basepage is to allow the include of pages in a way that mimics the 2.1.x behavior where page variables and links are interpreted relative to the currently displayed page. This is done with: (:include SomeOtherPage basepage='' :)
-or- (:include SomeOtherPage basepage={*$FullName} :)
It also allows GroupHeader and GroupFooter to have their page variables and links be relative to the currently displayed page (instead of GroupHeader and GroupFooter): ## PmWiki default Otherwise, using Include Other Pages inside of a GroupHeader would display ‘GroupHeader’ and not the name of the currently displayed page. The basepage= parameter is general enough that it can also be used as a templating engine, so that we can grab a template page containing variables that are then filled in with values from another page: (:include TemplatePage basepage=DataPage :)
And, of course, a single Template Page? can actually contain multiple templates delimited by anchors, so that we end up with a syntax eerily similar[1] to pagelist-templates: So then TemplatePage can use a syntax like: [[#abc]] ...template stuff here... [[#abcend]] and it’s possible to display TemplatePage as a template without it being interpreted… same as we do for Site.PageListTemplates. [1]Okay, maybe it’s not so eerie, given that the pagelist template code actually uses the same function as (:include:) to grab its templates. But it’s still a useful parallel.
Specifying variables as parametersYou can also specify variable values inline with the include statement, and refer to the variables in the template using the (:include TemplatePage variable1="value" variable2="value2":)
This assumes that a site has For example, on my included page (“template”) I might have this:
Then, including that section above (that section is available via the section
If a value contains spaces, quote it:
See also Specific markup
The purpose of See this thread and this thread for more info.
See Also
Styling NoteBy default, Included pages or lines cannot be distinguished from other text on the page. To provide a visual indication that this text is special, you can apply Wiki Styles. For example:
Parameter ReferencesAny parameters supplied to an include statement (whether they are keywords or not) are accessible inside the included page as a special Notes
Notes about use with conditional markupThe (:if some condition:)(:include SomePage#section:)(:if:)
But (:if some condition:)[[#section]]...[[#sectionend]](:ifend:)
When testing variables in included pages the context of the page (source or target) can be useful. See special references for details. Q What’s the maximum number of includes that can exist in a page? My site seems to stop including after 48 includes. ( $MaxIncludes )
By default, PmWiki places a limit of 50 include directives for any given page, to prevent runaway infinite loops and other situations that might eat up server resources. (Two of these are Group Header and Group Footer.) The limit can be modified by the wiki administrator via the Q Is there any way to include from a group of pages without specifying by exact name, e.g. between Anchor X and Y from all pages named IF Class?-* ? This can be achieved using page lists. Q There appears to be a viewing issue when the included page contains the (:title:) directive. In a default installation, the last title in the page overrides previous ones so you can place your (:title :) directive at the bottom of the page, after any includes. See also This page may have a more recent version on pmwiki.org: PmWiki:IncludeOtherPages, and a talk page: PmWiki:IncludeOtherPages-Talk. |