> ## Documentation Index
> Fetch the complete documentation index at: https://dokumentation.websale.de/llms.txt
> Use this file to discover all available pages before exploring further.

# Texts and messages

> The text sections of the shop configuration shop.config: headings, time units, free default texts, success and error messages for login, and the roughly 170 notification messages of the NotifyMessages-Txt section.

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

> [!NOTE]
>
> 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.

```ini theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/websale.json"]}}
<Captions-Txt>
   Payment          = Zahlungsart
   Delivery         = Versandart
   Address          = Rechnungsadresse
   DeliveryAddress  = Lieferadresse
   SearchAll        = Alles durchsuchen
   PleaseSelect     = Bitte wählen Sie
   BulkDiscountInfo = Infos zu den Staffelpreisen
   BulkDiscountFrom = ab
</Captions-Txt>
```

| Parameter | Heading for |
| - | - |
| `Payment` | the payment method |
| `Delivery` | the shipping method |
| `Address` | the billing address |
| `DeliveryAddress` | the delivery address |
| `SearchAll` | the entry in the search that searches all areas |
| `PleaseSelect` | the first entry of a selection list, which does not yet represent a selection |
| `BulkDiscountInfo` | the note on the tiered prices |
| `BulkDiscountFrom` | the quantity of a price tier |

> [!NOTE]
>
> 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

```ini theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/websale.json"]}}
<Buttons-Txt>
   TrustedShop = Anmeldung Geld-Zurück-Garantie
</Buttons-Txt>
```

| Parameter | Purpose |
| - | - |
| `TrustedShop` | Label of the button for registering for the money-back guarantee |

> [!WARNING]
>
> 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.

> [!WARNING]
>
> `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.

```ini theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/websale.json"]}}
<Times-Txt>
   Years   = Jahre
   Year    = Jahr
   Months  = Monate
   Month   = Monat
   Weeks   = Wochen
   Week    = Woche
   Days    = Tage
   Day     = Tag
   Hours   = Stunden
   Hour    = Stunde
   Minutes = Minuten
   Minute  = Minute
   Seconds = Sekunden
   Second  = Sekunde
</Times-Txt>
```

> [!NOTE]
>
> 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.

```ini theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/websale.json"]}}
<StandardMessages-Txt>
   Basket-Empty     = Ihr Warenkorb ist leer.
   Basket-MakeOrder = Sie können jetzt bestellen oder weitere Produkte auswählen.
   ProductRecmd     = Bitte klicken Sie auf den folgenden Link:
</StandardMessages-Txt>
```

| Parameter | Appears |
| - | - |
| `Basket-Empty` | on the basket page as long as the basket is empty |
| `Basket-MakeOrder` | on the basket page as soon as an order can be placed |
| `ProductRecmd` | in the recommendation email before the product link |

> [!NOTE]
>
> `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.

```ini theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/websale.json"]}}
<FreeMessages-Txt>
   Versandhinweis   = Lieferung innerhalb Deutschlands versandkostenfrei.
   Ruecksendung     = Rücksendungen sind 30 Tage lang möglich.
</FreeMessages-Txt>
```

In the template, you output these texts with the prefix `FMSG-`:

```html theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/websale.json"]}}
~FMSG-Versandhinweis~

{FMSG-Ruecksendung}
   <p>~FMSG-Ruecksendung~</p>
{/FMSG-Ruecksendung}
```

> [!WARNING]
>
> The legacy documentation mentions a limit of 100 texts. The shop system accepts 250 entries. Anything beyond that is silently discarded when reading in.

> [!NOTE]
>
> 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.

```ini theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/websale.json"]}}
<LoginSuccess-Txt>
   AddrData         = Ihre Adressdaten wurden erfolgreich gespeichert.
   AutoLogin        = Sie wurden erfolgreich automatisch angemeldet.
   ChangeEmail      = Ihre E-Mail-Adresse wurde erfolgreich geändert.
   ChangePW         = Ihr Passwort wurde erfolgreich geändert.
   RequirePW        = Ihr Passwort wurde Ihnen per E-Mail zugesendet.
   PasswordSet      = Das Passwort wurde erfolgreich gesetzt.
   PasswordSetLogin = Das Passwort wurde erfolgreich gesetzt und Sie wurden angemeldet.
</LoginSuccess-Txt>
```

| Parameter | Appears after |
| - | - |
| `AddrData` | the address data has been saved |
| `AutoLogin` | a successful automatic login |
| `ChangeEmail` | the email address has been changed |
| `ChangePW` | the password has been changed |
| `RequirePW` | the password has been sent by email |
| `PasswordSet` | a new password has been set via the link from the email |
| `PasswordSetLogin` | the same process, if the buyer was logged in at the same time |

### Double opt-in

| Parameter | Appears after |
| - | - |
| `NewCustomerDoubleOptInSent` | the activation email for a new account has been sent |
| `NewCustomerDoubleOptInSuccess` | the account has been activated via the link |
| `ChangeEmailDoubleOptInSent` | the confirmation email for a changed address has been sent |
| `ChangeEmailDoubleOptInSuccess` | the changed address has been confirmed |
| `DoubleOptInVoluntaryEmailVerificationSent` | the voluntary confirmation email has been sent |
| `DoubleOptInVoluntaryEmailVerificationSuccess` | the email address has been voluntarily confirmed |

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

| Parameter | Appears if |
| - | - |
| `Login` | email address and password do not match |
| `LoginUserID` | an invalid email address or an invalid user name was entered |
| `PW` | the password is invalid |
| `AutoLogin` | the automatic login failed |
| `NoInputLoginKnownUser` | a known customer entered neither address nor password |
| `NoInputLoginNewUser` | a new customer entered neither address nor password |

### Changing email address and password

| Parameter | Appears if |
| - | - |
| `Email` | an invalid email address was entered |
| `NewEmail` | an account already exists for the entered address |
| `NewEmailLength` | the new address is too short |
| `NewEmailMismatch` | the repeated address differs |
| `NewPWLength` | the new password is too short |
| `NewPWMismatch` | the repeated password differs |
| `NoInputChangeEmail` | inputs are missing when changing the address |
| `NoInputChangePassword` | inputs are missing when changing the password |

### Forgotten password

| Parameter | Appears if |
| - | - |
| `SendPW` | the password cannot be delivered because no email address is stored |
| `SetPasswordEmail` | the entered email address is unknown |
| `SetPasswordPermitted1` | the link for setting the password has expired |
| `SetPasswordPermitted2` | the buyer is already logged in and therefore cannot set a new password |
| `NoInputRequestSetPassword` | no email address was entered |

### Double opt-in

| Parameter | Appears if |
| - | - |
| `NoDoubleOptIn` | the account has not yet been activated |
| `InvalidDoubleOptInLink` | the activation link has expired |
| `DoubleOptInNewCustomerLoggedIn` | the buyer is already logged in to their account |
| `DoubleOptInChangeEmailWrongAccount` | the link does not belong to the account being accessed |

### Other

| Parameter | Appears if |
| - | - |
| `Input` | general errors occurred during input |
| `Zip` | no match was found for the entered postal code |
| `SubAccountCreate` | an account already exists for the address and a sub-account could be created |

> [!NOTE]
>
> 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.

```ini theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/websale.json"]}}
<Reseller-Txt>
   InputType-Value       = 0
   MaxSurcharge-Value    =
   Surcharge             = Reseller-Aufschlag
   HeaderNotify          = Bei Ihrer Reseller-Bestellung ist etwas unklar.
   SurchargeNotify       = Die Eingabe des Reseller-Aufschlages fehlt oder ist ungültig.
   MaxSurchargeNotify    = Der Reseller-Aufschlag darf maximal ~MaxSurcharge~ ~WS-Currency~ betragen.
   TotalSumNotify        = Der eingegebene Endbetrag ist kleiner als die bisherige Gesamtsumme.
   PaymentNotify         = Die Zahlungsart wurde auf Nachnahme gesetzt.
   DeliveryAddressNotify = Bei einer Reseller-Bestellung muss eine abweichende Lieferadresse angegeben werden.
   InputSuccess          = Ihre Eingaben wurden erfolgreich übernommen.
</Reseller-Txt>
```

| Parameter | Purpose | Values |
| - | - | - |
| `InputType-Value` | What the reseller enters. `0` means the surcharge, `1` the desired final total, from which the shop system calculates the surcharge. | `0`, `1`. Default `0` |
| `MaxSurcharge-Value` | Highest surcharge a reseller may enter. | Amount |
| `Surcharge` | Name of the surcharge in the display. | Text |

The remaining parameters are messages.

| Parameter | Appears if |
| - | - |
| `HeaderNotify` | one of the following messages is displayed, as a heading above it |
| `SurchargeNotify` | the surcharge is missing or invalid |
| `MaxSurchargeNotify` | the entered surcharge exceeds `MaxSurcharge-Value` |
| `TotalSumNotify` | the entered final total is below the previous grand total |
| `PaymentNotify` | the payment method was changed because of the reseller order |
| `DeliveryAddressNotify` | a different delivery address is missing |
| `InputSuccess` | the inputs were applied |

> [!WARNING]
>
> `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.

> [!NOTE]
>
> 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.

> [!WARNING]
>
> 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:

```text theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/websale.json"]}}
<Zahlungsart>-Clearing<Ereignis>
```

| Event | Meaning |
| - | - |
| `Deny` | The payment service provider declined the payment |
| `Error` | A technical error occurred, the payment method cannot be used at the moment |
| `Cancel` | The buyer cancelled the process at the payment service provider themselves |

Not every payment method knows all three events. The following table shows which ones exist.

| Payment method | Deny | Error | Cancel |
| - | - | - | - |
| `ApplePay` | yes | yes | yes |
| `Bill` | yes | yes | yes |
| `Billie` | yes | yes | yes |
| `Bizum` | yes | yes | – |
| `CCard` | yes | yes | yes |
| `ClickAndBuy` | yes | yes | – |
| `Debit` | yes | yes | – |
| `DebitCard` | yes | yes | – |
| `DirectDebitPayEX` | yes | yes | – |
| `DIRECTebanking` | yes | yes | – |
| `DotPay` | yes | yes | – |
| `GooglePay` | yes | yes | yes |
| `iDEAL` | yes | yes | – |
| `Installment` | yes | yes | yes |
| `Klarna` | yes | yes | yes |
| `OnlineTransfer` | yes | yes | – |
| `Paydirekt` | – | yes | yes |
| `Paymorrow` | – | yes | – |
| `PayPal` | yes | yes | – |
| `PayPalCheckout` | – | yes | – |
| `PayPalCheckoutAPM` | – | yes | – |
| `PayPalCheckoutPayLater` | – | yes | – |
| `PayPalCheckoutVault` | – | yes | – |
| `PayPalInvoice` | – | yes | – |
| `PayPalPlus` | – | yes | yes |
| `PayU` | yes | yes | – |
| `PostFinance` | yes | yes | – |
| `TWINT` | yes | yes | yes |

In addition, there are messages that do not fit this scheme:

| Parameter | Appears if |
| - | - |
| `PayPal-PaymentUnsupportedError` | the payment instrument selected at PayPal is not supported |
| `PaymentMissing` | no payment method is available anymore |
| `PaymentDeliverer` | the selected payment method does not match the selected shipping method |
| `PaymentInputSuffix` | the additional details for the selected payment method are missing |
| `DenyPayment` | a payment method was rejected |
| `DifferentDeliveryAddressError` | the payment method does not allow a different delivery address |
| `DifferentDeliveryAddressForNewUserError` | the payment method does not allow a different delivery address for new customers |
| `DelivCountryDiffersNotAllowed` | billing and delivery country differ but must be the same |
| `DelivCountryDiffers` | billing and delivery country differ |
| `DelivCountryDiffersWrongDelivCountry` | the delivery country is not permitted |
| `SessionLockedForOnlineclearing` | the session is locked during an online payment process |
| `CCard-Input`, `CCard-Saved`, `CCard-Deleted` | credit card data was entered, saved or deleted |
| `Debit-Input` | direct debit data was entered |
| `PPCVault-Saved`, `PPCVault-Deleted` | a PayPal payment instrument was saved or deleted |
| `PPCVault-SaveError`, `PPCVault-DeleteError` | an error occurred in the process |

> [!NOTE]
>
> 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.

> [!WARNING]
>
> `CCard-Input` and `CCard-Saved` are deprecated. Credit card data is now entered at the payment service provider, not in the shop.

> [!WARNING]
>
> 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

| Parameter | Appears if |
| - | - |
| `ProductNotFound` | the product is no longer available |
| `ProductSoldOut` | the product is sold out |
| `CategoryNotFound` | the category was not found |
| `ProductMinQuantity` | the minimum quantity is not reached |
| `ProductMaxQuantity` | the maximum quantity is exceeded |
| `ProductMaxQuantity-UserOrder` | the customer-specific maximum quantity is exceeded |
| `ProductMaxQuantity-Inventory` | the maximum quantity is limited by the stock level |
| `ProductUnitFactor` | the quantity is not divisible by the packaging unit |
| `UserUnitFactorError` | a customer-specific packaging unit is violated |
| `QuantityScaling` | the quantity scaling is violated |
| `GreetingProductsMaxQuantity` | the maximum quantity for greeting products is exceeded |
| `TextInputFieldError` | a mandatory text input field for the product is empty |
| `OnlyAsSetChild` | the product can only be ordered as part of a set |
| `VoucherProduct` | the product can only be ordered with a voucher |
| `ProductLicenses-1`, `ProductLicenses-2` | a license condition of the product is not met |
| `HappyHourProductInactive` | a HappyHour product is outside its time window |
| `ProductPremiumProductToBasket` | a premium product cannot be added to the basket |
| `ProductSubscriptionProductNotOrderable` | a subscription product cannot be ordered |
| `EBookCheckError` | an e-book cannot be ordered |
| `DistributionServiceNotOK`, `DistributionServiceLowQuantity` | the distribution service rejects the product or reports insufficient stock |

> [!NOTE]
>
> 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.

> [!NOTE]
>
> 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

| Parameter | Appears if |
| - | - |
| `Basket-MinOrder` | the minimum order value has not been reached |
| `Basket-MinQuantityGroup` | a minimum quantity per group has not been reached |
| `Basket-MaxProductsReached` | the maximum number of items has been reached |
| `MaxBasketPositions` | the same from the perspective of the item limit |
| `MaxBasketQuantities` | the maximum quantity across all items has been reached |
| `Basket-ProductsW2POnly` | the basket only contains web-to-print products |
| `NoBasketInput` | the product could not be added to the basket due to a missing quantity or selection |
| `LoggedOutUserAddProductToBasketError` | a buyer who is not logged in wants to add a product to the basket |
| `GiftProductSubTotalUnderValue` | the value of goods is not sufficient for a free gift |
| `PlaceOrder-NegativeTotalSum` | the grand total would be negative |
| `Conditions` | the terms and conditions were not accepted |
| `Order-Error` | the order failed in general |
| `DisableShop` | the shop is switched off |
| `WSFreightCostsError` | the shipping costs could not be determined |
| `TaxJar-GetSalesTaxError`, `TaxCaseError` | the tax calculation failed |
| `BPOInputCheckError` | an input for a product option is incorrect |
| `ShareEmailWithShippingProviderError` | the consent to pass on the email address failed |

> [!NOTE]
>
> `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

| Parameter | Appears if |
| - | - |
| `DelivererMissing` | no shipping method is available anymore |
| `DelivererAdditionalInput` | additional details for the shipping method are missing |
| `DeliveryDate` | a requested delivery date is missing |

### Addresses

| Parameter | Appears if |
| - | - |
| `Addr-Input` | the billing address is incomplete or incorrect |
| `Addr-Saved`, `Addr-Deleted` | the billing address was saved or deleted |
| `DelivAddr-Input` | the delivery address is incomplete or incorrect |
| `DelivAddr-Saved`, `DelivAddr-Deleted` | the delivery address was saved or deleted |
| `DelivAddr-Invalid` | the selected delivery address is no longer valid |

> [!NOTE]
>
> 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

| Parameter | Appears if |
| - | - |
| `EmtpyMemoList` | the memo list is empty |
| `MemoListLogin` | a buyer who is not logged in wants to add something to the memo list |
| `MemoListFull` | the memo list is full |
| `Bank-Saved`, `Bank-Deleted` | bank data was saved or deleted |
| `OrderHistory` | the order history needs a message |
| `EmptyReOrder` | there are no reorderable products |
| `SavedBasket-Created` | a saved basket was created |
| `SavedBasket-Saved` | a saved basket was updated |
| `SavedBasket-Replaced` | a saved basket was replaced |
| `SavedBasket-Added` | the current basket was added to a saved one |
| `SavedBasket-Deleted` | a saved basket was deleted |
| `SavedBasket-DeletedEntry` | an item was deleted from it |
| `SavedBasket-DescrEmpty` | the name is missing |

> [!WARNING]
>
> 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.

### Search

| Parameter | Appears if |
| - | - |
| `SearchMinLen` | the search term is too short |
| `SearchNoMatch` | the search found nothing |

### Wish list and recommendation

| Parameter | Appears if |
| - | - |
| `ProductFromDifferentWishLists` | products from different wish lists are to end up in one basket |
| `ProductRecmd-Input` | the inputs for the recommendation are incorrect |
| `ProductRecmd-EmailError` | the entered email address is invalid |

> [!NOTE]
>
> 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

| Parameter | Appears if |
| - | - |
| `ProductPrimePackageAlreadyPurchased` | a Prime package that has already been purchased is to be bought again |
| `ProductPrimeProductNoLogIn` | a buyer who is not logged in wants to order a Prime product |
| `ProductPrimeProductNoValidPrimePackage` | a logged-in buyer without a valid Prime package wants to order a Prime product |

> [!WARNING]
>
> 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

| Parameter | Appears if |
| - | - |
| `NoOffers` | there are no customer-specific offers |
| `OffersBasket-1` | there are already products in the basket and an offer can only be ordered separately |
| `OffersBasket-2` | there is already an offer in the basket |
| `IDSNoBasketInput` | not all passed products could be added to the basket |
| `IDSParameterMissing` | a parameter is missing when calling the interface |
| `InstantVoucherError` | an error occurred with a printable purchase voucher |
| `PDFGeneratorError` | a PDF file could not be generated |
| `RPDE_Labelprint-BasketError` | a Labelprint24 product could not be added to the basket |
| `TrustedShopsAdv` | Trusted Shops buyer protection is not available |
| `FastOrderConfigured` | the quick order settings were applied |
| `Inquiry-Error` | an error occurred with an inquiry |

### 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.

```ini theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/websale.json"]}}
<NotifyMessages-Txt>
   SecureCookieTokenError            =
   SSLError                          =
   SecureLoadTemplateError           =
   StandardTemplateLoadTemplateError =
</NotifyMessages-Txt>
```

| Parameter | Appears if |
| - | - |
| `SecureCookieTokenError` | no cookie could be set |
| `SSLError` | a secure page is to be opened in HTTP mode |
| `SecureLoadTemplateError` | a template from the `SecureLoadTemplates` section is to be opened in HTTP mode |
| `StandardTemplateLoadTemplateError` | a page of the checkout process, the customer account or the login is to be opened in HTTP mode |

> [!NOTE]
>
> 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.


## Related topics

- [Rating configuration prodrating.config](https://dokumentation.websale.de/en/v8s/referenz/konfigurationen/bewertungskonfiguration-prodrating-config.md)
- [Default texts](https://dokumentation.websale.de/en/v8s/einstellungen/standardtexte.md)
- [Order quantity of a product](https://dokumentation.websale.de/en/v8s/produkte/bestellmenge-eines-produkts.md)
- [MSG- (Messages)](https://dokumentation.websale.de/en/v8s/referenz/tags/msg-meldungen.md)
- [FMSG- (Free default texts)](https://dokumentation.websale.de/en/v8s/referenz/tags/fmsg-freie-vorgabetexte.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.