Skip to main content
A template runs in many places in the shop, often even the same template on several pages. For an include or a header area to adapt to this, it needs an answer to three questions: Which page am I on, how did I get here, and where in the product range am I right now. This is exactly what the ST- tags on this page answer. The other states of the prefix are on separate pages.
  • Reference: ST- (customer and login)
  • Reference: ST- (checks in the order process)
  • Reference: ST- (payment and express checkout)
  • Reference: ST- (delivery, tax and multiple delivery)
  • Reference: ST- (operating modes and technology)
All ST- tags are pure bracketings. They exist in a positive and a negative version, but neither as a single tag nor as a loop. In the overview table at the end, this is therefore the same for all tags.

​
Which page the buyer is on

The previous example for ST-PlaceOrderPage closes both areas with {/ST-PlacedOrderPage}, that is, with one d too many. This is a different tag name, so the area is never closed.
The main purpose of these tags is controlling includes. A header or footer area that is included on all pages uses them to hide the parts that get in the way on a specific page.
ST-StartPage only applies if the start page was called as the start page. A redirect to it, for example after login in a closed shop, and loading the start page template via a template link do not set this state. The template is then the same, but the state is different.
ST-BasketPage also applies if the basket page is reloaded via a background request.
ST-LoginPage exists in the shop system but is not described in the previous documentation. It adds the login page to the other page states.

​
The order has been placed

ST-PlacedOrder does not distinguish by page but by point in time: it applies as soon as the order has been created successfully.
In the explanatory text, the previous documentation uses the positive notation both times, even where it means the negative bracketing. The correct form is {!ST-PlacedOrder} for the case that the order has not yet been placed or an error has occurred.
An order is considered placed when the buyer has clicked the order button and no error occurred. If the process fails, the bracketing does not apply.

​
How the page was called

ST-Addr_Order and ST-Addr_Manage are a pair. The same address page serves in the order process and in account management, and the two tags distinguish the two paths. This lets you label the buttons appropriately instead of offering “Continue to the next order step” in both cases.
ST-Addr_Manage exists in the shop system but is not described in the previous documentation.
ST-FormMethodGet is not described either. It applies if the form was submitted via GET and the session parameter is in the address. It is intended for templates that work with link optimisation and must take the browser’s back button into account.
ST-Ajax is suitable for areas that should only be output in the response to a background request, for example an HTML fragment without a page skeleton.

​
Where in the category tree

Four bracketings answer questions about the current category. All four require an argument.
ST-CatLevel() takes two limits separated by a comma. The first is the lower limit, the second the upper limit, and either of them may be left empty.
Without a selected category, the level is zero. A bracketing with an open lower limit therefore applies, while one with a lower limit of one or more does not.
These four tags strictly require an argument. Empty parentheses make them an invalid tag. They are also invalid as a single tag and as a loop.
The previous example for ST-CatIndex() checks for 1-111 in the negative bracketing but describes the index 1-1234 below it. The example is self-contradictory.
ST-CatLastTopIndex() exists in the shop system but is not described in the previous documentation. It falls back on the most recently visited main category and is therefore useful on pages that have no category of their own, for example the basket.
ST-CatIndex() compares with the index of the current category, ST-CatTopIndex() with its top level. For a design per product range area, the main category is almost always the right choice.

​
Around the displayed product

A main product of a grouping cannot be ordered itself. The quantity field and order button therefore belong in the negative bracketing. In the shop system, the tag applies as soon as the product has subordinate products.
  • Reference: APD- (alternative product data)
  • Guide: Grouping products

​
Deprecated tags

ST-PR_FromCategory was intended to indicate whether a product was called from a regular category, in order to hide paging and the way back to the list when the buyer came via the search or the basket.
The tag still exists in the shop system and checks an internal flag that apparently is no longer set in this version. The bracketing therefore does not apply, and no replacement is planned. Do not use it in new templates.

​
Tags at a glance

All tags on this page are permitted on all templates. ST-ParentProduct requires an active product, the four category tags a loaded category. ST-Change and ST-Addr_Order only produce a meaningful result in the order process.
  • Guide: Includes and template logic
  • Reference: CAT- (categories)
  • Reference: ST- (operating modes and technology)