Skip to main content
Almost every text that a buyer reads in the shop and that does not come from the product data or the template is in one of the text sections of the shop.config. This applies to headings just as much as to the message that a credit card payment was declined. The advantage of this separation: you can reword these texts per subshop, translate them and adapt them to a target group without touching any template. The price for this is that an unfilled parameter leads to an empty spot in the shop without a warning appearing anywhere. This page covers the sections that hold texts exclusively or predominantly. The texts of individual functions are described with the respective function. Reference: Shop configuration shop.config, overview of all sections
All texts in these sections may contain HTML, including links. The examples in the legacy documentation make use of this, for example with a link to the password request in the middle of an error message. After a change, check whether the HTML is still balanced, because an unclosed element breaks the page on which the message appears.

Captions-Txt

Holds the headings that the shop system sets itself, mainly in the checkout process.
The section knows exactly these eight parameters; no further headings can be stored here. PleaseSelect is the only one with a built-in fallback text. If it is left empty, “Bitte wählen Sie” appears. All others remain empty if you leave them empty.
Guide: Changing standard texts

Buttons-Txt

The section contains exactly this one parameter. The legacy documentation describes it as the place for “the labels of the automatically generated buttons” and gives the basket button as an example. There is no parameter for this here. You set button labels in the template.
TrustedShop belongs to an outdated form of the Trusted Shops integration. The parameter is not needed for the current integration.
Guide: Trusted Shops, Changing standard texts

Times-Txt

Holds the words for time units that the shop system uses in time specifications, for example for the remaining time of a HappyHour product. There is a singular and a plural form for each unit.
The plural form always comes before the singular form. The shop system chooses the appropriate form itself. Fill in both, otherwise the word is missing for a value of exactly 1.
Guide: Changing standard texts

StandardMessages-Txt

Holds messages that the shop system outputs depending on the state of the page, without an error being present.
Basket-Empty and Basket-MakeOrder are both output by the MSG-Basket_Standard tag. Which of the two texts appears is decided by the shop system based on the state of the basket. So there is only one tag in the template.
Guide: Standard texts

FreeMessages-Txt

Here you create your own texts that are not linked to any function of the shop system. You assign the name yourself, and you retrieve the text in the template under this name.
In the template, you output these texts with the prefix FMSG-:
The legacy documentation mentions a limit of 100 texts. The shop system accepts 250 entries. Anything beyond that is silently discarded when reading in.
The name becomes the tag exactly as you write it. Therefore avoid spaces and special characters and stick to letters, digits and the underscore. A name that matches an existing name wins over the shop tag of the same name, because the shop system checks the free texts first. So choose names that differ from the names of the MSG- tags.
Guide: Defining free default texts. Reference: FMSG- (free default texts)

LoginSuccess-Txt

Holds the success messages related to login, customer account and double opt-in.

Double opt-in

Guide: Secure login procedure, Forgotten password, Double opt-in, Persistent login, Voluntary confirmation of the email address

LoginError-Txt

The counterpart: the error messages related to login and customer account.

Logging in

Changing email address and password

Forgotten password

Double opt-in

Other

For security reasons, the activation link from the double opt-in is only valid for one hour. State this time limit in InvalidDoubleOptInLink, otherwise buyers will not know why their link no longer works and will try again with the same link.
Guide: Secure login procedure, Forgotten password, Double opt-in, Multiple accounts, Enabling login in the checkout process, Persistent login

Reseller-Txt

Configures reseller orders and also holds their messages. A reseller buys in the shop and adds their own surcharge to the value of the goods.
The remaining parameters are messages.
InputType-Value only knows 0 and 1. Any larger value is reset to 0, so the reseller then enters the surcharge and not the final total.
The tags MaxSurcharge and WS-Currency can be used in MaxSurchargeNotify. Insert the amount into the message instead of writing it out in the text, otherwise it will no longer be correct after a configuration change.
Guide: Supporting reseller orders

NotifyMessages-Txt

By far the largest text section. This is where the notification and error messages are that the buyer sees when something does not go as expected: a product is sold out, the payment was declined, the minimum order value has not been reached. These texts are output by the MSG- tags. Which text appears is decided by the shop system based on the state of the session, not by the template. The template only contains an MSG- tag at the appropriate place, for example MSG-PlaceOrder_Notify on the order overview.
A parameter left empty means that nothing at all appears at the relevant place. The buyer then sees that their click had no effect but does not find out why. Therefore go through the section once completely instead of limiting yourself to the parameters in the example of the legacy documentation.

Payment methods: the naming scheme

More than half of all parameters in this section belong to payment methods and follow a fixed scheme:
Not every payment method knows all three events. The following table shows which ones exist. In addition, there are messages that do not fit this scheme:
In the shop system, SessionLockedForOnlineclearing is written with a lowercase c in “clearing”. The legacy documentation uses an uppercase C in one place. Both spellings are accepted; the shop compares parameter names without regard to case.
CCard-Input and CCard-Saved are deprecated. Credit card data is now entered at the payment service provider, not in the shop.
The message for SessionLockedForOnlineclearing is the most important one in the entire section. It appears when the buyer returns from the payment service provider without a payment having arrived in the shop, for example because they used the browser’s back button. Without a text, they are faced with a page on which they cannot proceed. Include the link from WS-UnlockSessionOnlineClearingLink in the text so that they can find their way back to their basket.

Products and quantities

The local tags Name, VarName and VarValue can be used in ProductSoldOut, the latter two also as brackets. This lets you name the affected product including its variant in the text. In ProductMaxQuantity and its two variants, PR-Name, PR-ProductName, PR-MaxQuantity and PR-Unit are available.
If ProductMaxQuantity-Inventory is empty, the shop system falls back on ProductMaxQuantity. So you only need to make the distinction where the buyer needs it.

Basket and order completion

WS-MinOrder-Value and WS-Currency can be used in Basket-MinOrder, and the tags WS-GiftProductMissingSubTotal and WS-CurrencySymbol in GiftProductSubTotalUnderValue. Do not write out the amounts, otherwise text and configuration will drift apart.

Shipping and delivery

Addresses

The tag D-EditLink can be used in DelivAddr-Invalid. Use it to take the buyer directly to address management instead of making them search for it.

Customer account, memo list and saved baskets

The parameter really is called EmtpyMemoList and not EmptyMemoList. The transposed letters are in the shop system’s name table itself. So write the name exactly like this, otherwise the message remains empty.

Wish list and recommendation

In the shop system, the parameter is called ProductRecmd-EmailError. The legacy documentation writes it with an uppercase M as ProductRecmd-EMailError. Both spellings are accepted.

Prime shopping

These three messages only appear if the respective parameter is filled. If it is left empty, the note only appears on the order overview, that is, much later in the checkout process. Only the tag PR-Name can be used in all three texts; other tags are not replaced.

Modules and interfaces

Secure session

These four messages appear on the notification page ws_notify.htm and concern session management with secure cookies. Since all shop pages are loaded in SSL mode, in practice usually only the first one is needed.
Whether these messages are displayed in your shop at all must be enabled separately by WEBSALE technical staff. If needed, ask your WEBSALE contact.

Deprecated entries

The shop system’s name table contains seven placeholders named deprecated or DEPRECATED. They come from discontinued functions and only hold the positions in the table. A parameter with this name in your configuration has no effect.