Configuration migration

This page serves as a migration aid for the configuration of shops that previously run on V8s and are to be transferred to the new version. It helps you map existing configuration sections and settings of the previous configuration files to the corresponding configuration nodes of the new version, so that the shop can be configured identically or as comparably as possible after the migration.

---

​

Shop configuration shop.config

The following overview contains the configuration sections of the V8s shop.config in alphabetical order. A complete description of all sections can be found in the V8s documentation. Each section has been mapped to the corresponding configuration node of the new version where possible. This way, the overview supports you in implementing existing V8s configurations identically or comparably in the new version. If sections or individual parameters are missing without a mapping, our support team will be happy to help via the Support Center.

​

Alphabetical overview of the V8s sections

• <AcceptTermsAndConditions>
  • checkout.checkout.freeFields
• <AddDomains>
  • urls.redirects
• <AdditionalProductFieldsInBasket>
  • Removed without replacement; every product data field can be displayed in the basket without additional configuration.
• <AddressFields-Actions>
  • Removed without replacement; reloads, refreshes, etc. can be added directly in the template without configuration based on accounts.addressFieldsSettings
• <AddressFields-AlternativeText>
  • accounts.addressFieldsSettings
• <AddressFields-InputVisibility>
  • accounts.addressFieldsSettings
• <AddressFields-ReadOnly>
  • accounts.addressFieldsSettings
• <AddressFields-Standards>
  • accounts.addressFieldsSettings
• <AddressFields-Txt>
  • accounts.addressField
  • accounts.addressFieldsSettings
• <AddressMaxInputLen>
  • accounts.addressField
• <AgreementCookies>
  • general.consentCookieGroup
  • general.consentCookieService
• <ASSE>
  • general.asse
• <Basic>
  • general.general
  • general.language
  • general.subshop and general.subshopView
  • general.testMode
• <BasketEntries>
  • basket.basket
• <BonusPoints>
  • Not yet available
• <Buttons-Txt>
  • Removed without replacement; corresponding texts are set directly in the template or via text snippets.
• <Captions-Txt>
  • Removed without replacement; corresponding texts are set directly in the template or via text snippets
• <CatProdCount>
  • Removed without replacement; since the number of products in a category can be loaded directly in the template via the category data without additional configuration, for example $myVariable.productsCount
• <ChangeEmailDoubleOptInMail>
  • actions.emailUpdate
• <Currency-Txt>
  • finance.currency
• <CustomerMail>
  • actions.checkoutConfirm
• <A-Suffix1> to <A-Suffix100>
  • accounts.addressField
  • accounts.addressFieldsSettings
• <D-Suffix1> to <D-Suffix100>
  • accounts.addressField
  • accounts.addressFieldsSettings
• <DeepLinks>
  • Configurable via “SEO URLs” in the Admin Interface or PUT seo/urls
• <DeleteAccountDoubleOptInMail>
  • actions.accountDelete
• <Delivery> and <+Deliverer>
  • checkout.shippingMethod
• <DeliveryAddressFields-Standards>
  • accounts.addressFieldsSettings
• <DeliveryAddressFields-Txt>
  • accounts.addressField
  • accounts.addressFieldsSettings
• <DeliveryAddressSelection>
  • Removed without replacement; corresponding texts are set directly in the template or via text snippets
• <DeliveryDate>
  • Not yet available
• <DelivererProductDependencies-Definitions>
  • Coming soon
• <DesignControl>
  • security.method
• <DirectOrder>
  • checkout.directOrder
  • actions.directOrder
• <eMarketingManager>
  • Removed without replacement; since there are no longer any fixed template assignments.
  • Sign-ups and sign-outs can be integrated on any template via the $wsNewsletter module.
  • This also applies to a sign-up during the order process or at login.
• <eMarketingManager-Txt>
  • actions.newsletter*
• <ExternalSearch>
  • Removed without replacement; since there is no support for native connections to external search service providers. Integration takes place client-side via WebComponents or JavaScript plus data feeds for transmitting the product data.
• <FilterAndSort>
  • WEBSALE Search
• <GenericEmails>
  • messages.emails
• <ImageLinks>
  • Removed without replacement; since there are no longer any automatically generated button icons for the storefront. Buttons can be created completely freely for the storefront using the template language or the Storefront API.
• <InputCheck> and <+InputCheck>
  • addressCheck.*
  • data.checker*
  • <+InputCheck> type=zip → general.zipCodes
• <Inventory>
  • content.inventory
  • actions.inventoryReserve
• <LinkNameEncoding>
  • urls.urls
• <Login>
  • b2b.access
  • accounts.accountRestrictions
  • actions.login
  • actions.passwordForgotten
  • actions.resetPassword
  • actions.login
• <MaxCatProducts>
  • WEBSALE Search
• <NewCustomerDoubleOptInMail>
  • actions.accountActivateOptIn
• <NewCustomerMail>
  • actions.accountRegister
• <NotifyMessages-Txt>
  • Depending on the case actions.*
• <OrderConditions>
  • checkout.checkout
  • Partially actions.checkoutConfirm
• <OrderNowMail>
  • content.inventory
• <OrderOptions1> to <OrderOptions5>
  • checkout.checkout
• <OrderSpecialInput>
  • checkout.checkout
• <PaymentApplePay-Txt>
  • payment.payment
  • payment.paypalCheckout or
  • payment.computopHosted
• <PaymentAccount-Txt>
  • Not currently supported
• <PaymentBill-Txt>
  • payment.payment; for offline payment methods no further configuration is required
  • For online payment methods, additionally the appropriate provider configuration, for example payment.paypalCheckout
  • For Stripe, the payment method is also created via payment.payment; the included Stripe payment options are then generally provided via payment.stripe or the provider.
• <PaymentBillie-Txt>
  • Currently only via payment.stripe
• <PaymentCashOnDelivery-Txt>
  • payment.payment
• <PaymentCreditCard-Txt> and <Card1> to <Card5>
  • payment.payment
  • payment.payment; for online payment methods additionally the appropriate provider configuration, for example payment.paypalCheckout. For Stripe, the payment method is also created via payment.payment; the included Stripe payment options are then generally provided via payment.stripe or the provider.
• <PaymentDebitNote-Txt> and <PaymentDebitNote-Country>
  • payment.payment; for offline payment methods no further configuration is required. For online payment methods additionally the appropriate provider configuration, for example payment.paypalCheckout. For Stripe, the payment method is also created via payment.payment; the included Stripe payment options are then generally provided via payment.stripe or the provider.
• <PaymentEnvironmentDependencies-Definitions>
  • Coming soon
• <PaymentDIRECTebanking-Txt>
  • Sofortüberweisung is no longer supported
• <PaymentGooglePay-Txt>
  • Configuration via payment.payment and payment.paypalCheckout or payment.computopHosted
• <PaymentIDeal-Txt>
  • Currently only via payment.stripe
• <PaymentInstallment-Txt>
  • payment.payment; for online payment methods additionally the appropriate provider configuration, for example payment.paypalCheckout. For Stripe, the payment method is also created via payment.payment; the included Stripe payment options are then generally provided via payment.stripe or the provider.
• <PaymentKlarna-Txt>
  • Currently only via payment.stripe
• <PaymentOnlineTransfer-Txt>
  • Giropay is no longer supported
• <PaymentPaydirekt-Txt>
  • Paydirekt is no longer supported
• <PaymentPaymorrow-Txt>
• <PaymorrowDebit-Mapping>
• <PaymorrowDebit-NotifyMessages>
• <Paymorrow-Mapping>
• <Paymorrow-NotifyMessages>
  • Not currently supported
• <PaymentPayPalCheckout-Txt>
• <PaymentPaypal-Txt>
• <PaymentPayPalCheckoutAPM_BANCONTACT-Txt>
• <PaymentPayPalCheckoutAPM_BLIK-Txt>
• <PaymentPayPalCheckoutAPM_EPS-Txt>
• <PaymentPayPalCheckoutAPM_GOOGLEPAY-Txt>
• <PaymentPayPalCheckoutAPM_APPLEPAY-Txt>
• <PaymentPayPalCheckoutAPM_IDEAL-Txt>
• <PaymentPayPalCheckoutAPM_MYBANK-Txt>
• <PaymentPayPalCheckoutAPM_PRZELEWY24-Txt>
• <PaymentPayPalCheckoutPayLater-Txt>
• <PaymentPayPalInvoice-Txt>
  • Configuration via payment.payment and payment.paypalCheckout
• <PaymentPayPalPlus-Txt>
  • Removed without replacement; PayPal only via payment.payment and payment.paypalCheckout
• <PaymentPayU-Txt>
  • Not currently supported
• <PaymentPostFinance-Txt>
  • Currently only via payment.stripe with primary support of PostFinance Card and PostFinance Pay as debit/payment methods
• <PaymentPrepayment-Txt>
  • payment.payment
• <PaymentProductDependencies-Definitions>
  • Coming soon
• <PaymentTWINT-Txt>
  • Currently only via payment.stripe
• <PaymentUserDef1-Txt> to <PaymentUserDef5-Txt>
  • payment.payment
• <PaymentXXX-Txt>
  • payment.payment
• <PDFGenerator>
  • Removed without replacement; since any template can be rendered as a PDF using the link parameter wsFilter=pdf
• <PriceFormat>
  • general.numberFormat
• <ProductComparison>
  • No configuration anymore, but purely via the templates by storing the desired products to be compared via the $wsStore module and then comparing the product fields with the functions < > or ==
• <ProductItemSearch>
  • WEBSALE search
• <ProdRecmdMail>
  • Not currently supported
• <ProductSort>
  • WEBSALE Search
• <RegistrationMail>
  • actions.accountRegister
• <SearchFactFinder-Filter>
  • Removed without replacement; since there is no support for native connections to external search service providers. Integration takes place client-side via WebComponents or JavaScript plus data feeds for transmitting the product data.
• <SecureLoadTemplates>
  • Removed without replacement; since SSL is standard
• <SecureLogin>
  • actions.checkPasswortStrength
• <SecuredPassword>
  • accounts.autoLogin
• <SEOProductFields>
  • seoMetaData.*
• <SEOProductFields-Text>
  • seoMetaData.*
• <SetPasswordMail>
  • actions.passwordForgotten
  • actions.resetPassword
• <ShopAdminMail>
  • Via the LogManager (Logs) service in the Admin Interface
• <ShopTransferMail>
  • Via the LogManager (Logs) service in the Admin Interface
• <StandardMessages-Txt>
  • Mostly actions.* or a template/text snippet topic
• <Templates>
  • Removed without replacement; only the templates start.htm, category.htm, and product.htm are fixed and may not be renamed. All other functions may be loaded on any template
• <Times-Txt>
  • Removed without replacement; texts are set directly in the template or via text snippets
• <TopRank>
  • urls.urls
  • urls.redirects
  • general.sitemap
• <UserData>
  ??????
• <VAT>
  • finance.taxRates
  • finance.taxRatesAddition
  • finance.taxes
• <VerifyCustomerData>
  • accounts.addressField
  • or mostly actions.* or a template/text snippet topic
• <Voucher-Txt>
  • actions.voucherAdd
  • actions.voucherDelete
• <WelcomeCookie>
  • No configuration anymore, but can be mapped purely via the template with the $wsCookies module
• <WSPMUpdateMail>
  • Removed without replacement; the WSP Manager no longer exists

​

Country list country.dat

• country.dat
• deliv_country.dat
  • general.country

​

Title list title.dat

• title.dat
  • general.title

​

Salutation list salutation.dat

• salutation.dat
  • general.salutation

​

Product rating prodrating.config

• prodrating.config
  • actions.productRating*