Project-related #global invocations

The requirements of a website can make it necessary to access the settings or other project information. For example, if a language change is to be enabled within the website it is useful to determine the defined project languages beforehand.

For such purposes, the system object #global enables the project's properties to be accessed. This is done using the expression #global.project, which returns an object of data type Project.

The most important invocations are listed in the following table:

Examples

Several examples of use of the instruction within templates are shown in the following. The examples are intended to clearly show the specific effect of the instruction and provide help for the template developer when creating their own templates.

The examples displayed here must be adjusted for use within a project! For example, variable names must be changed to the specific variable names of the project in which the instruction is to be used.

1st Example: Drop-down box with all generated project languages

<select size="1" name="language" onchange="window.location.href=this.options[this.selectedIndex].value">
  $CMS_FOR(l, #global.project.languages)$
    $CMS_IF(l.shouldGenerate)$
      <option value="$CMS_REF(#global.node, lang:l.abbreviation)$">$CMS_VALUE(l.name + " (" + l.abbreviation + ")")$</option>
    $CMS_END_IF$
  $CMS_END_FOR$
</select>

In the example, all project languages are determined with #global.project.languages . The $CMS_FOR(...)$ instruction is now used to treat each individual project language. If the Generate Language option is activated for the language (project settings: Lanugages; Check with .shouldGenerate()), a drop-down box entry is output. The name of language and in addition (enclosed in brackets) the abbreviation are displayed in the drop-down box. The aim of the entry is the current page in the relevant language.

Exemplary output:

<select size="1" name="language" onchange="window.location.href=this.options[this.selectedIndex].value">
  <option value="/preview/671041/show/site/DE/current/671044/681046">Deutsch (DE)</option>
  <option value="/preview/671041/show/site/EN/current/671044/681046">English (EN)</option>
  <option value="/preview/671041/show/site/ES/current/671044/681046">Español (ES)</option>
</select>

2nd Example: Output of a picture in all project resolutions

$CMS_FOR(r, #global.project.resolutions)$
  <p>
    $CMS_IF(r.isOriginal)$
      <img src="$CMS_REF(media:"florida")$"/>
      <p>Picture -
        unscaled
      - ($CMS_VALUE(ref(media:"florida").width)$x$CMS_VALUE(ref(media:"florida").height)$)</p>
    $CMS_ELSE$
      <img src="$CMS_REF(media:"florida", res:r)$" />
      <p>Picture -
        $CMS_IF(r.width > 0)$
          width-scaled
          $CMS_IF(r.height > 0)$
            and height-scaled
          $CMS_END_IF$
        $CMS_ELSIF(r.height > 0)$
          height-scaled
        $CMS_END_IF$
      - ($CMS_VALUE(ref(media:"florida", res:r).width)$x$CMS_VALUE(ref(media:"florida", res:r).height)$)</p>
    $CMS_END_IF$
  </p>
$CMS_END_FOR$

In the example, all resolutions are determined with #global.project.resolutions . The $CMS_FOR(...)$ instruction is now used to treat each resolution individually:

• If it is the original resolution (.isOriginal), the picture is output unscaled with the text "Picture - unscaled - " and the width and height in pixels.
• For other resolutions the picture is output with the corresponding resolution. At the same time it is determined whether the width and/or height of the picture is scaled and then the corresponding width and height is output in pixels. A picture is always scaled if either the width or the height specification in the resolution has a value greater than 0.

Exemplary output:

<p>
  <img src="/preview/671041/show/media/DE/current/773042/ORIGINAL"/>
  <p>Picture - unscaled - (4134x2766)</p>
</p>
<p>
  <img src="/preview/671041/show/media/DE/current/773042/W100" />
  <p>Picture - width-scaled -(100x67)</p>
</p>
<p>
  <img src="/preview/671041/show/media/DE/current/773042/H100" />
  <p>Picture - height-scaled -(149x100)</p>
</p>

3rd example: Filtering project properties

In some cases it can be of benefit to filter some of the amount of project properties (as for example languages, resolutions, template sets, users) by specific criteria for becoming able to apply specific methods in them.

For this purpose the method .filter can be used. (See also page Mapping expressions (lambda).)