Staging System / Developement System / Testing System (without additional costs for plugins)

by ACRIS E-Commerce GmbH

Premium Extension

Rating: 4.8

(21 reviews)

Downloads: 530

Set up a test environment simply, quickly and easily. No additional shopware / plugin licenses required. DSGVO compliant! Copying of customers/orders on demand.

Annually €24.92* /month €359.88 * €299.00* /year 16.92% discount In comparison to the regular monthly price

Monthly €29.99* /month Cancelable monthly

Compatible with:

6.2.0 - 6.7.6.2

Includes:

Free trial month

The subscription starts with a free trial month during which it can be canceled at any time.

All updates

During the subscription all released updates are included for free

Support from the Extension Partner

In case you have any questions or problems with your extension you can always ask the Extension Partner for help during the subscription.

Description

Highlights

Create test environment in just a few clicks
No extra plugin costs: plugins work without relicensing
Set up as many test environments as you like

Features

Easy setup: create a test environment with a few clicks
DSGVO compliant, as customer data and orders are only copied on request.
Easy copying or deleting of test environment (file structure and database)

About the Extension

Why a test environment / staging environment / test system / staging system makes sense:

Test updates, plugins, themes and settings without risk
Simple operation, reduction to the essentials
No additional shopware or plugin license required
DSGVO compliant, as customers and orders are only transferred to the test system on request,

Configuration

In the Shopware Admin area under Settings -> Plugins -> Staging-System has been added. In the first step please "add" a new staging-system.

Internal name: is only used for the overview if you create multiple staging / test systems.
Directory: into this directory (e.g. staging) the complete Shopware 6 system will be copied and can be accessed after creation in the frontend under www.Domain.com/staging or admin area www.Domain.com/staging/admin
Database host: if the database is located on the same server as the Shopware system's website, use the default value; if not, use the host from the database server. Default value: "localhost".
Database name: enter the name for the test environment database
Database user: enter the user for the test environment database
Database password: enter the password for the test environment database
Shop owner e-mail address: If a different shop owner e-mail address is to be used for the test system than in the live system. Otherwise leave it empty.
Maintenance mode: If this is activated, the test system will be put into maintenance mode after the test environment has been created.
Copy orders: for DSGVO reasons the orders should not be copied for test systems, but this is possible with set hacking.
Copy customers: for DSGVO reasons the customers should not be copied for test systems, but this is possible with set hacking.

Before the actual copying takes place, please save the configuration and then the button "Create Staging System" is active.
The creation of the staging system / test environment can take some time.

In the overview of our plugin you can see when the staging environment was created and you can easily "overwrite" or delete it with the saved data. If the staging environment is deleted, both the subdirectory and the database will be deleted.

Technical Requirements / Notes

Creation of an empty database required (for staging / test database)
Additional settings may be necessary for the hoster (e.g. for TimmeHosting the nginx configuration for Shopware 6 must be assigned to the subfolder)
If cron jobs are required for staging, these must be set up at the hoster.
If the staging environments are not created correctly, it could be due to a timeout. In this case, please increase the php.ini and timeout of PHP Scripts. max_execution_time.
Make sure that there is enough space on the server - everything is copied 1:1, which means that shopware and all content data is duplicated.

Why a test environment / staging environment / test system / staging system makes sense:

Test updates, plugins, themes and settings without risk
Simple operation, reduction to the essentials
No additional shopware or plugin license required
DSGVO compliant, as customers and orders are only transferred to the test system on request,

Configuration

In the Shopware Admin area under Settings -> Plugins -> Staging-System has been added. In the first step please "add" a new staging-system.

Internal name: is only used for the overview if you create multiple staging / test systems.
Directory: into this directory (e.g. staging) the complete Shopware 6 system will be copied and can be accessed after creation in the frontend under www.Domain.com/staging or admin area www.Domain.com/staging/admin
Database host: if the database is located on the same server as the Shopware system's website, use the default value; if not, use the host from the database server. Default value: "localhost".
Database name: enter the name for the test environment database
Database user: enter the user for the test environment database
Database password: enter the password for the test environment database
Shop owner e-mail address: If a different shop owner e-mail address is to be used for the test system than in the live system. Otherwise leave it empty.
Maintenance mode: If this is activated, the test system will be put into maintenance mode after the test environment has been created.
Copy orders: for DSGVO reasons the orders should not be copied for test systems, but this is possible with set hacking.
Copy customers: for DSGVO reasons the customers should not be copied for test systems, but this is possible with set hacking.

Technical Requirements / Notes

Creation of an empty database required (for staging / test database)
Additional settings may be necessary for the hoster (e.g. for TimmeHosting the nginx configuration for Shopware 6 must be assigned to the subfolder)
If cron jobs are required for staging, these must be set up at the hoster.
If the staging environments are not created correctly, it could be due to a timeout. In this case, please increase the php.ini and timeout of PHP Scripts. max_execution_time.
Make sure that there is enough space on the server - everything is copied 1:1, which means that shopware and all content data is duplicated.

Details

Available: English, German
Latest update: 23 January 2026
Publication date: 15 June 2020
Version: 5.4.1
Category: Administration

Resources

Reviews (21)

Average rating

4.8

Based on 21 reviews

4.7 Functionality

4.8 Usability

4.7 Documentation

4.9 Support

Write a review

If you downloaded this extension you can write a review in the Shopware Account.

Write a review

Sort by

Achtung - hat den kompletten Shop unbenutzbar gemacht!

2.0

by Ein User

18 March 2021 13:44

Das Plugin hat nach dem installieren und anschließendem erstellen einer Testumgebung dazu geführt, dass auf allen Produktseiten im Shop (inkl. Startseite) nur noch "Es ist ein Problem aufgetreten" stand (wohlgemerkt im Live-Shop!). So war der komplette Shop nicht mehr benutzbar. Finde ich total krass - immerhin sollte das Plugin eigentlich im Live-Shop gar nichts machen und nur die Daten in eine neue, leere DB kopieren sowie die Shopdateien in einen Unterordner kopieren und dort entsprechende Konfigurationseinstellungen vornehmen. Natürlich habe ich den Cache geleert, Indizies aktualisiert und alles versucht, auch das entfernen der Testumgebung über die Benutzeroberfläche, hat aber auch nichts gebracht. Immerhin ist nach dem deinstallieren und löschen des Plugins (+ Cache leeren) nun alles wieder in Ordnung, der Shop konnte halt solange eine Weile nicht benutzt werden. Den Support habe ich nicht getestet, sondern das Ding natürlich sofort deinstalliert. Da zahle ich lieber mehr und nehme was, das dann auch funktioniert. Shopware-Version 6.3.4.1

1.0 Functionality

1.0 Usability

1.0 Documentation

3.0 Support

by ACRIS E-Commerce GmbH 12 April 2021 19:06

Lieber "Ein User" - leider konnten wir keinen Kontakt mit Ihnen aufnehmen, entsprechend können wir auch keine Hilfestellung leisten. Das von ihnen geschilderte "Problem" kommt wahrscheinlich daher, dass sie nicht wie beschrieben eine neue, leere Datenbank angegeben haben, sondern die vom Hauptshop verwendet haben. Entsprechend wurden die Daten der "Kopie" in die Hauptdatenbank geschrieben - wir haben nun eine Prüfung eingebaut, sodass auch unerfahrene User keinen Fehler mehr machen können.