addedValues Plugin

addedValueMacros.page

Syntax

{addedValueMacros.page(reportID, , contextKey="", leadDelimiter = "[[", postDelimiter = "]]")}

• reportID - the name of an addedValues message report.
• contextKey - optional, a reference to a context, which defaults to current context. For
  1. messages - a messagenumber or shortcut, defaults to current page.
  2. members - a member key, defaults to current member.
  3. gems - a gem number or gem shortcut, no default.
  4. cornershop - a member key, defaults to basket of current member
• leadDelimiter - optional, start delimiter used by report.
• postDelimiter - optional, end delimiter used by report

Examples

Semantics

The page macro is the main way that a web designer makes use of the values of variables stored in a message. It's best considered as a template for a portion of the page. Reports can be simple or very complex, can call macros passing variables values from the current message, can include other reports (using the page macro!) and so on.

The leadDelimiter, postDelimiter and flDebug parameters are a legacy of the development phase and would rarely be used anymore.

; Error encountered are reported as HTML comments with an explanatory text, use view source in your browser to see them; such as

<!-- controlled report topsecret not accessible -->

See also

• Reports