~MSG-Basket_Notify~
{/MSG-Basket_Notify} ``` The area tag takes effect if a message is present. The single tag of the same name inside it outputs the text. > [!WARNING] > > Never place the single tag without an area tag. If there is no message, the text remains empty, but the surrounding HTML is still on the page. The visitor then sees an empty colored box. ```html theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/websale.json"]}} {!MSG-DirectOrder_Notify}Alles in Ordnung, Sie können bestellen.
{/!MSG-DirectOrder_Notify} ``` > [!NOTE] > > The negative area tag is the opposite case and is suitable for the normal state. Not every message needs it; for success messages, the opposite case is usually uninteresting. ## Where the texts come from The texts are not in the template but in the shop configuration `shop.config`. Which section is responsible depends on the type of message. | Section | Contains | | - | - | | `{MSG-Voucher_error(2)}Diese Gutscheinnummer ist ungültig.{/MSG-Voucher_error(2)} {MSG-Voucher_error(4)}Dieser Gutschein ist abgelaufen.{/MSG-Voucher_error(4)} {MSG-Voucher_error(5)}Dieser Gutschein wurde bereits eingelöst.{/MSG-Voucher_error(5)}
{/MSG-Voucher_error} ``` > [!NOTE] > > Write the individual cases inside the area tag without an argument. This way, the surrounding element, that is, the colored box, is only in the template once, and it also appears if a code occurs for which you have not provided a separate text. > [!WARNING] > > In this case, also output the code, for example in an HTML comment. Otherwise, the visitor is faced with an empty box, and support has nothing to go on. ### Vouchers `MSG-Voucher_success` knows two codes. | Code | Meaning | | - | - | | 1 | The voucher number was accepted | | 2 | The voucher was removed | `MSG-Voucher_error` knows 27 codes. | Code | Cause | | - | - | | 1 | Input was blocked after too many failed attempts | | 2 | The voucher number is invalid | | 3 | The voucher is not yet valid | | 4 | The voucher has expired | | 5 | The voucher has already been used | | 6 | Personalized voucher, the buyer is not logged in | | 7 | The universal voucher has already been used | | 8 | The voucher does not match the products in the basket | | 9 | Personalized voucher, only for new customers | | 10 | Customer-specific new customer voucher, the buyer is not logged in | | 11 | The voucher is only valid for new customers | | 12 | The voucher is only valid for new customers, the buyer is not logged in | | 13 | The maximum number of redemptions has been reached | | 14 | The voucher does not match any product in the basket, the order is blocked | | 15 | Login is required for this voucher number | | 16 | The voucher is not permitted for this customer account | | 17 | Universal voucher bound to the customer account, login required | | 18 | Universal voucher bound to the customer account, this account does not match | | 19 | Login is required for this voucher number | | 20 | The voucher cannot be removed | | 21 | The voucher does not match, checked via a product data field | | 22 | The voucher does not match, checked via the stock level | | 23 | The buyer is excluded from voucher promotions | | 24 | The voucher can only be redeemed in the app | | 25 | A customer discount is already stored for the buyer | | 26 | The voucher number was entered more than once | | 27 | The voucher cannot be combined with other vouchers | For code 3, `MSG-Voucher_error_validfrom` and `MSG-Voucher_error_validuntil` state the validity period. ```html theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/websale.json"]}} {MSG-Voucher_error(3)} Dieser Gutschein ist erst ab dem ~MSG-Voucher_error_validfrom~ gültig. {/MSG-Voucher_error(3)} ``` ### Subscription module `MSG-Subscription_success` knows seven codes. | Code | Meaning | | - | - | | 1 | The product was added to the subscription list | | 2 | The subscription was paused | | 3 | The subscription was reactivated | | 4 | Quantity or interval was changed | | 5 | The subscription was deleted | | 6 | New subscriptions were initiated | | 7 | The bank details were applied to subscriptions | `MSG-Subscription_error` knows eleven named codes and two ranges. | Code | Cause | | - | - | | 1 | The buyer is not logged in | | 2 | Quantity or interval is missing or invalid | | 3 | A paused subscription cannot be changed | | 4 | The product is not a subscription product | | 5 | Set products are not supported | | 6 | No product variant was selected | | 7 | The product number was not found | | 8 | There are no subscriptions in the "new" state | | 9 | The selected payment method is not permitted for subscriptions | | 10 | For direct debit, the assignment of the bank details is missing | | 11 | The permitted number of subscriptions per customer account has been reached | | from 900 | internal error codes for diagnosis | | from 2000 | errors when immediately triggering a subscription order | > [!WARNING] > > The codes from 900 and from 2000 are intended for diagnosis and not for the visitor. Only output them internally, for example in an HTML comment. ### Prime packages and Prime products `MSG-PrimeProduct_error` concerns products reserved for Prime customers. | Code | Cause | | - | - | | 1 | Prime products in the basket, the buyer is not logged in | | 2 | Prime products in the basket, the buyer lacks the permission | `MSG-PrimeShopping_error` concerns the Prime packages themselves. | Code | Cause | | - | - | | 1 | Prime packages in the basket, the buyer is not logged in | | 2 | At least one of the packages has already been purchased | | 3 | A package is not valid for the selected billing country | `MSG-PrimePackagesManage` concerns management in the customer account. | Code | Meaning | | - | - | | 1 | The Prime package was canceled | | 2 | The package was already canceled or has expired | | 3 | The package was not found | > [!NOTE] > > The two Prime error messages belong on the basket page, the login page and the order overview. If one of the three is missing, the buyer is stuck at that point without explanation. ### Updated online prices | Code | Occasion | | - | - | | 1 | The buyer updated the prices themselves | | 2 | The prices were updated automatically | | 3 | The prices were updated during the order overview | ## Addresses The messages for the billing address and the delivery address are structured symmetrically. For each `MSG-Addr_` tag, there is an `MSG-DelivAddr_` tag with the same task. | Tag | Message | | - | - | | `MSG-Addr_Notify` | the summary message for the billing address | | `MSG-Addr_saved` | the billing address was saved | | `MSG-Addr_InputError_SalutFirstName` | salutation and first name may not match | | `MSG-Addr_InputError_NumericZip` | the postal code contains non-numeric characters | | `MSG-Addr_InputError_ZipCity` | postal code and city do not match | | `MSG-Addr_InputError_DifferentDelivCountry` | a different delivery country is not possible | | `MSG-Addr_InputError_DifferentDelivCountryVAT1` | the same, due to the VAT ID entered | | `MSG-Addr_InputError_DifferentDelivCountryVAT2` | the same, second variant | | Tag | Message | | - | - | | `MSG-DelivAddr_Notify` | the summary message for the delivery address | | `MSG-DelivAddr_saved` | the delivery address was saved | | `MSG-DelivAddr_deleted` | the delivery address was deleted | | `MSG-DelivAddr_InputError_SalutFirstName` | salutation and first name may not match | | `MSG-DelivAddr_InputError_NumericZip` | the postal code contains non-numeric characters | | `MSG-DelivAddr_InputError_ZipCity` | postal code and city do not match | | `MSG-DelivAddr_InputError_DifferentDelivCountry` | a different delivery country is not possible | | `MSG-DelivAddr_InputError_DifferentDelivCountryVAT1` | the same, due to the VAT ID entered | | `MSG-DelivAddr_InputError_DifferentDelivCountryVAT2` | the same, second variant | > [!NOTE] > > The `_Notify` tags summarize, while the `_InputError_` tags name the individual reason. It is common to show both: at the top, the notice that something is unclear, and at the affected field, the individual message. ## Login and customer account | Tag | Message | | - | - | | `MSG-Login_Notify` | the messages related to login | | `MSG-UserAccount_Notify` | the messages on the customer account overview | | `MSG-AutoLogin_success` | the automatic login worked | | `MSG-AutoLogin_error` | the automatic login failed | | `MSG-SubAccountCreate` | an account already exists for this email address | | `MSG-SetPasswordEmailSent` | the email for resetting the password was sent | | `MSG-DoubleOptInNewCustomerSent` | the activation link for a new account was sent | | `MSG-DoubleOptInNewCustomerSuccess` | the customer account was activated | | `MSG-DoubleOptInChangeEmailSent` | the link for changing the email address was sent | | `MSG-DoubleOptInChangeEmailSuccess` | the email address was applied | | `MSG-DoubleOptInVoluntaryEmailVerificationSent` | the voluntary confirmation email was sent | | `MSG-DoubleOptInVoluntaryEmailVerificationSuccess` | the email address was voluntarily confirmed | | `MSG-DoubleOptInDeleteAccountEmailSent` | the link for deleting the account was sent | | `MSG-DoubleOptInDeleteAccountSuccess` | the customer account was deleted | > [!NOTE] > > `MSG-UserAccount_Notify` accesses the `