Türchen 5: How to install Magento 2 with German (de_DE) backend and frontend


These instructions describe the setup of a German language Magento 2 installation with the necessary settings for sales in Germany. Firstly, a variant of the installation of Magento 2 is described in brief. Following this, the necessary steps for the adaption to Germany by means of the language pack and the extension MageSetup are given in detail.

[Read these instructions in German here: Magento 2 komplett auf Deutsch installieren.]

System requirements

Magento 2 generally requires a system with the following specifications:

Webserver Nginx version 1.8 or higher, or alternatively Apache 2.2 or 2.4
PHP PHP 5.6 or PHP 7.0
MySQL MySQL 5.6 or 5.7, or alternatively MariaDB 10.0 or higher

Additionally, access to the console (e.g. via SSH) is mandatory. A FTP-based installation is generally possible, but in this case automated customizations for Germany could not be applied with this method. More detailed informations concerning requirements and the required PHP modules are provided by Magento.

Magento 2 installation

Generally there are different ways to install Magento 2. In the following instruction the installation by means of composer is described exemplarily and reduced to the essentials. An overview of the installation methods is provided here by Magento.

Composer installation

To be able to realize the installation with Composer, it has to be installed at first:

Download of Magento 2

Now the installation can be executed using Composer:

This command downloads the necessary Magento 2 files and writes them to the directory /var/www/magento2.

Installation of Magento 2

The actual installation of Magento 2 can now be performed with the web installer. Therefore the shop URL has to be opened in a browser. Here the installation credentials (including URL and database name) must be entered.

Installation of the language pack

After the installation of Magento 2 has been completed or if the language pack shall be integrated into an existing system, initially the package has to be downloaded using composer:

As appropriate the frontend JavaScript translations have to be deleted and the static contents have to be newly generated afterwards:

Now it is possible to switch to German language in admin panel.

Change backend language

After selecting System > Permissions > All Users the users of the admin panel can be opened for editing separately and switched to German language using the field Interface Locale. After their next login they find themselves in a German Backend.


Change frontend language

To change the language of the shop fronted generally or for a specific store view to German after navigating to Stores > Settings > Configuration the scope can be defined in the upper left corner. Afterwards in General > General > Locale Options the Use Default checkbox can be deactivated for the field Locale in which the language can be changed to German.

Installation of MageSetup

The extension MageSetup automatically applies a series of adjustments in the shop. So the settings for the particular country do not all have to be made manually. This includes tax rules, tax rates, general business terms, and notifications for shipping costs.

The installation of MageSetup is performed using Composer:

Then the module must be activated:

After the installation and activation of the module have been completed the actual changes can be made:

When everything has completely run in console the adjustments in the shop have already been made. Now further changes concerning legal contents (e.g. general terms of business) can be made in the admin panel as appropriate.


  • 6. May 2018

    Server mit 16GB RAM
    12 Vcores
    Frisches Magento 2.2.3 Setup
    PHP 7.0
    20.000 Produkte (simple products)

    1. $ composer require firegento/magesetup2:dev-develop
    2. $ bin/magento module:enable FireGento_MageSetup
    3. $ bin/magento setup:upgrade
    4. $ bin/magento magesetup:setup:run de

    Bei Start processor: tax geschieht auch nach 15 Stunden Wartezeit nichts. Läuft der Vorgang tatsächlich so lange, oder scheint es Probleme zu geben?
    Sehe ich irgendwo den Fehler in einer Log?! Wenn ja, wo liegt diese?

    Ich würde mich über jeden Hinweis freuen.


  • 8. July 2019

    Man kann den Prozess deutlich beschleunigen, wenn man vorher den Indexer für alles auf “Update on Schedule” stellt.

    Es liegt am Speichern der/aller Produkte im TaxSubProcessor: Dort wird immer das komplette Produkt gespeichert, obwohl nur ein Attribut geändert wird.
    Ich habe einen Patch in der Arbeit, der über eine “ProductResource” nur das betreffende Attribut speichert. Dadurch wird der Prozess gefühlt 100mal schneller. Leider entspricht er wg. der direkten Verwendung des “ObjectManager” (noch) nicht den Magento2 Coding-Richtlinien.

    Wer aber auf das Problem stößt ist ja evtl. froh mit meinem Branch zu experimentieren: https://github.com/hawkeyevc/firegento-magesetup2


Your email address will not be published. Required fields are marked *