Contact

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

(24 reviews)
597 downloads
Set up a test environment simply, quickly and easily. No additional shopware / plugin licenses required. DSGVO compliant! Copying of customers/orders on demand.
Monthly
€29.90* / month
Cancelable monthly
Annual
16.67% discount
€24.92 / month
€358.80* €299.00* / year
Go to Shopware Store

Technical Information

Category Administration
Created At June 10, 2020
Last Updated August 12, 2026
Languages de_DE, en_GB
Keywords staging, testsystem, stagingsystem, staging store, test shop
Technical name AcrisStaging

Highlights

  • Create test environment in just a few clicks
  • Optionally secure the staging system with password protection
  • 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
  • Password protection for the staging system can be enabled
  • DSGVO compliant, as customer data and orders are only copied on request.
  • Easy copying or deleting of test environment (file structure and database)

Purpose of the plugin

The plugin allows staging and test environments to be created and managed directly from the Shopware Administration. This makes it possible to test updates, plugins, themes, configurations and individual customizations independently of the live shop. The required shop files, media and database contents are automatically transferred to the test environment.

Easily create and manage staging systems

Staging environments are configured and created directly in the Shopware Administration. The test system can be created in a subdirectory or at a custom server path. Existing staging systems can be recreated, overwritten or deleted.

Custom APP URL and individual domains

A custom APP URL can be defined for the staging system. This means that the test environment is not limited to the live shop domain in combination with a subdirectory, but can instead be accessed via a separate subdomain or custom path, for example. In addition, individual staging URLs can be defined for the domains of specific sales channels.

Selectively transfer data

It can be individually defined which data should be copied to the test environment. Customers and orders can be excluded from the transfer for data protection reasons. In addition, unnecessary table contents and directories can be excluded from the copying process to optimize the creation of the staging system.

Operate the test environment securely

The staging system can be protected with password protection and optionally placed into maintenance mode after creation. Email sending can be disabled in the test environment and search engine indexing can be prevented using the corresponding settings.

Flexible settings for development and testing

For development and testing purposes, DEV mode can be activated, additional administrators can be created and further settings for the staging environment can be configured. Status information and logs help monitor the creation process.

Optional staging system on an external server (In-App Purchase)

Via a separately available In-App Purchase, the staging system can be created entirely on an external server. The SSH/SFTP connection details and the desired target path are entered and checked before creation. The required files, media and database are then transferred to the external server. When deleting the staging system, the corresponding remote directory can also be removed after explicit confirmation.


Installation

  • Open the Plugin Manager via Settings > System > Plugins
  • Upload, install and activate the plugin

Create staging system

Settings → Extensions → Staging System

Basic settings

  • Internal name: Internal name of the staging system. The name is used solely to distinguish the staging system within the Administration and is not displayed in the storefront.
  • Path type: Defines where the staging system is created. Depending on the available functionality, the staging system can be created in a subdirectory, at a custom path on the same server or on an external server.
Staging in a subdirectory
  • Directory: Name of the directory in which the staging system is created. Enter the directory name without a leading or trailing slash, for example staging. The staging system is then accessible by default via the existing shop URL with the directory appended, for example myshop.com/staging.
Staging at a custom path
  • Directory: Name of the staging directory, for example staging.
  • Custom path: Absolute server path under which the staging directory should be created, for example /var/www/. The specified directory name is automatically appended to this path.
  • Test path: Checks whether the specified path can be used for the staging system. Among other things, the plugin checks whether the target path is accessible and whether files already exist there.

The custom path defines where the files are stored. Public access to the staging system must additionally be configured via the staging URL and, if necessary, the web server configuration.

Staging on an external server

With the additional feature “Staging on an external server”, the complete staging system can be set up on a separate server via SSH/SFTP.

  • Remote SSH host: Hostname or IP address of the server on which the staging system should be created.
  • Remote SSH port: SSH port of the external server. Port 22 is usually used by default.
  • Remote SSH user: Username for the SSH/SFTP connection to the external server.
  • Remote SSH password: Password of the specified SSH user.
  • Test connection: Checks whether a connection to the external server can be established using the specified SSH credentials.
  • Remote path: Absolute file system path on the external server under which the staging system should be installed, for example /var/www/staging.

The parent path must already exist on the external server. The final required directory can be created by the plugin. The document root of the domain being used must point to the public directory of the Shopware installation. If absolute file paths are used in the shop or in extensions, for example for imports or exports, these may need to be adjusted to the new server path.

Configure staging URL

  • Automatically generated URL: Uses the existing shop URL and appends the configured staging directory. For a directory named staging, this could result in myshop.com/staging, for example.
  • Custom domain / subdomain: Allows a separate domain or subdomain to be used for the staging system, for example staging.myshop.com.
  • APP URL: Complete URL of the staging system when using a custom domain or subdomain. This URL is stored as the APP_URL of the staging system.

DNS entries as well as the web server or vHost configuration for a custom domain or subdomain must be configured outside the plugin. A custom APP URL is required for a staging system on an external server.

Edit staging domains

  • Staging domain: Defines the URL under which the respective existing sales channel domain should be accessible in the staging system.

This makes it possible, for example, to access multiple storefronts via separate staging subdomains. Each staging domain must be unique and cannot be assigned to multiple sales channel domains at the same time.

Configure database

  • Database host: Host of the database server. If the database is located on the same server, 127.0.0.1 can be used, for example.
  • Database port: Port of the database server. Port 3306 is used by default for MySQL or MariaDB.
  • Database name: Name of the database to be used for the staging system.
  • Database user: Username for accessing the staging database.
  • Database password: Password of the specified database user.
  • Test connection: Checks whether a connection to the staging database can be established successfully using the entered credentials.

General settings

  • Shop operator email address: Email address that is stored as the shop operator email address in the Shopware master data of the newly created staging system.
  • Internal comment: Optional comment field for internal information about the staging configuration, for example its intended use or special characteristics of the environment.

Secure email sending and access

Email sending

  • Disable email sending in the staging system: Disables email sending within the staging system. This prevents order confirmations, registration emails or other messages from accidentally being sent to real recipients during testing.
Search engines
  • Set the “robots” meta name to “noindex,nofollow”: Adds the corresponding robots directive to the staging system pages and instructs search engines not to index the pages or follow links contained on them.
  • Create a robots.txt and block all bots: Creates a robots.txt file that prevents search engine crawlers from crawling the staging system.
Password protection
  • Enable password protection: Activates additional access protection for the staging system.
  • Username: Username used to access the protected staging system.
  • Password: Password used to access the staging system.
Maintenance mode
  • Maintenance mode: Activates Shopware maintenance mode for the staging system after creation. This means that the storefront is only accessible to appropriately approved IP addresses.

Configure data transfer

  • Copy orders: Defines whether existing orders from the live system should be transferred to the staging system. If this option is disabled, existing orders, order line items, deliveries and transactions, among other data, are not copied.
  • Copy customers: Defines whether existing customer data from the live system should be transferred. If this option is disabled, existing customers, customer addresses and other customer-specific data are not copied.
  • Do not copy unnecessary table contents: Excludes data from tables that are not required for a typical staging system. This can include shopping carts, logs, queue data, version data and other temporary data. This reduces the amount of data to be transferred and can speed up the creation of the staging system.
  • Do not copy Shopware Migration database tables: Displayed when the Shopware Migration Assistant is installed. The sometimes very large migration tables are not populated with existing data.

Configure creation

  • Create staging system via message queue: Creates the staging system using the Shopware message queue. The individual processing steps are executed sequentially via the queue.
  • Set staging system to DEV mode: Activates Shopware or Symfony development mode for the new environment. This is particularly useful for development and troubleshooting.
  • Disable Symfony Toolbar: Disables the Symfony Web Debug Toolbar even when DEV mode is enabled. Since the toolbar can display technical and sensitive system information, disabling it is particularly recommended for publicly accessible staging systems.

Exclude directories from staging

  • Excluded directories: Paths to files or directories that should be excluded from the transfer. The paths are specified relative to the Shopware root directory, for example public/media.

Create additional admin users

  • First name: First name of the Administration user.
  • Last name: Last name of the Administration user.
  • Email address: Email address of the Administration user. The address must be unique.
  • Username: Username used to log in to the Administration of the staging system.
  • Password: Password used to log in as the user.
  • Administrator: Defines whether the user receives full administrator permissions.
  • User interface language: Defines the language in which the Shopware Administration is displayed for the user.
  • Time zone: Defines the time zone of the Administration user.
  • Job title: Optional job title of the user.
  • Roles: Allows existing Shopware roles to be assigned if the user should not receive full administrator permissions.

Remove staging system

  • Clear staging database: Removes the existing tables and contents from the configured staging database. The staging system will no longer be functional until it is created again.
  • Delete staging file system: Deletes the files from the configured staging directory. For an external staging system, the corresponding directory on the external server is removed.

Plugin configuration

Extensions → My extensions → Staging System → Configure

  • If active, “meta name=robots content=noindex,nofollow” is set: Indicates whether the current installation has been marked with “noindex,nofollow” by the plugin. This field is for status information only and cannot be changed manually.
  • If active, this is a staging system: Indicates whether the current Shopware installation has been marked as a staging system by the plugin. This field is also for status information only.

Staging on an external server

The plugin optionally provides the additional feature “Staging on an external server”. This allows the staging system to be set up completely on a separate server instead of on the same server as the live system. The additional feature can be purchased directly via the Administration. To do so, the shop must be connected to a Shopware account under Extensions → My extensions → Shopware account. After activation, an additional option for creating the staging system on an external server is available under the path type.

Frequently Asked Questions

Es wurden keine Fragen gefunden. Kontaktieren Sie uns, wenn Sie konkrete Fragen haben!
Version Date Compatibility Changelog
5.8.2 10 August 2026 >=6.7.0.0 <6.8.0.0
  • - Fixed: The button "Open Shopware account" in the card of the additional feature did not react to a click.
  • - Fixed: If the additional feature cannot be loaded from the Shopware Store, the reason of the store is shown instead of the general hint to log in.
5.8.1 6 August 2026 >=6.7.0.0 <6.8.0.0
  • - Fixed: Creating the staging system could fail with "mkdir(): File exists" when the shop uses a symlinked var/cache or var/log directory (e.g. shared-directory deployments).
5.8.0 6 August 2026 >=6.7.0.0 <6.8.0.0
  • - Added #32627: Staging system on an external server via SSH/SFTP, in the CS version with the in-app purchase "Staging on an external server".
  • - Added #38174: Own APP URL (custom domain/subdomain) for the staging system instead of the automatically generated URL.
  • - Added: Configurable staging domains per sales channel domain.
5.7.4 14 July 2026 >=6.7.0.0 <6.8.0.0
  • - Fixed: With password protection enabled, the staging Administration kept prompting for the password and reloaded endlessly, while the storefront worked. The password prompt is now only shown for actual page loads, so the Administration and its background requests are no longer blocked.
5.7.3 6 July 2026 >=6.7.0.0 <6.8.0.0
  • - Fixed: Setting file permissions on the public folder during staging creation invoked a separate shell process for every single file instead of a single recursive operation, which could take an extremely long time on shops with large media libraries. This caused the message queue worker to hang, resulting in "Scheduled tasks overdue" warnings and other queued tasks not being processed. Permissions are now applied recursively in a single operation.
5.7.2 2 July 2026 >=6.7.0.0 <6.8.0.0
  • - Fixed: Staging system creation failed on MySQL 8.4+ with "Failed to add the foreign key constraint. Missing unique key for constraint" during database import, because MySQL 8.4 enables stricter foreign key validation (restrict_fk_on_non_standard_key) by default. The database import now disables this check for the import session.
5.7.1 2 July 2026 >=6.7.0.0 <6.8.0.0
  • - Deactivating mail sending on staging now disables mail delivery for all sales channels.
5.7.0 1 July 2026 >=6.7.0.0 <6.8.0.0
  • - Added HTTP Basic Authentication password protection for staging environments.
  • - Password is hashed with bcrypt before storage; Symfony toolbar is hidden when protection is enabled.
5.6.5 30 June 2026 >=6.7.0.0 <6.8.0.0
  • - Fixed: The system files copy process (files directory) could get stuck in a running state if the message queue worker was terminated during copying. Added recovery mechanism that detects this state on the next invocation and marks the process as finished.
  • - Fixed: The system files copy status was not reset before a new staging creation attempt, which could prevent copying if a previous attempt had failed.
  • - Improved: Directory copying now uses a single bulk shell copy operation instead of file-by-file copying when no subdirectories are excluded, significantly reducing the time needed to copy large directories.
5.6.4 22 June 2026 >=6.7.0.0 <6.8.0.0
  • - Optimized path loading for the staging system buttons to open the staging system in the admin.
5.6.3 15 June 2026 >=6.7.0.0 < 6.8.0.0
  • - The profiler configuration file is no longer created if the web-profiler-bundle is not installed.
5.6.2 11 June 2026 >=6.7.0.0 < 6.8.0.0
  • - Renamed profiler configuration file for staging systems to ensure correct loading order.
5.6.1 8 June 2026 >=6.7.0.0 < 6.8.0.0
  • - Fixed: Replaced direct `require_once vendor/autoload.php` with PSR-4 namespace registration on the existing Composer ClassLoader to avoid registering a second autoloader, which caused a warning in Frosh Tools ("2 autoloaders registered: acris/staging").
5.6.0 3 June 2026 >=6.7.0.0 < 6.8.0.0
  • - Added option to disable Symfony toolbar when staging system is set to dev mode.
5.5.4 1 June 2026 >=6.7.0.0 < 6.8.0.0
  • - Improved copying shopware files.
5.5.3 28 May 2026 >=6.7.0.0 < 6.8.0.0
  • - Adds the database tables of the ACRIS stock notification plugin to the list of unnecessary tables so they are ignored during the staging database migration.
5.5.2 27 May 2026 >=6.7.0.0 < 6.8.0.0
  • - Fixed: Reset copyMediaFolder and copyThumbnailFolder status to null before dispatching queue messages to prevent stuck running state on new staging creation attempt.
5.5.1 5 May 2026 >=6.7.0.0 < 6.8.0.0
  • - Fixed: SHOPWARE_ES_THROW_EXCEPTION is automatically set to 0 in staging .env files to prevent Elasticsearch errors during Shopware updates
  • - Behoben: SHOPWARE_ES_THROW_EXCEPTION wird in den Staging .env-Dateien automatisch auf 0 gesetzt, um Elasticsearch-Fehler bei Shopware-Updates zu verhindern
5.5.0 4 May 2026 >=6.7.0.0 < 6.8.0.0
  • - Feature: Added custom staging path option. Users can now choose between creating the staging system in a subfolder (default behavior) or specifying a custom absolute server path for the staging root directory. A new "Path type" selector is available in the staging configuration form. When "Custom path" is selected, a text field appears where the absolute path can be entered (e.g. /var/www/html/staging-custom). A "Test path" button allows validating the path before starting the staging creation process.
5.4.14 29 April 2026 >=6.7.0.0 < 6.8.0.0
  • - Fixed: "MySQL server has gone away" error during database import caused by large serialized cart objects in the `cart_tmp` table exceeding the MySQL `max_allowed_packet` limit. The `cart_tmp` table is now always excluded from the staging database export (structure is still copied, only data is skipped) since it contains transient in-progress cart data that is never needed in a staging environment.
  • - Improvement: Added MySQL session timeout variables (`wait_timeout`, `interactive_timeout`, `net_read_timeout`, `net_write_timeout`) to the PDO connection used during database import to prevent connection drops on long-running imports.
5.4.13 27 April 2026 >=6.7.0.0 < 6.8.0.0
  • - Fixed: Staging creation getting stuck at step 5/8 (StagingCopyPublic) on shops with large media libraries. The Symfony Finder was configured with incorrect notPath patterns ("public/media/*", "public/thumbnail/*") that never matched because the Finder is already scoped inside the public/ directory. Replaced with exclude(["media", "thumbnail"]) which prevents the Finder from entering those directories entirely, eliminating the PHP memory/timeout issue that caused the worker to die silently and leave the queue stuck with no visible error.
5.4.12 23 March 2026 >=6.7.0.0 < 6.8.0.0
  • - Applies the in_process retry mechanism to the CopyMediaFolder and CopyThumbnailFolder queue handlers so that if the database connection is lost after a completed copy operation, the status update is automatically retried on the next queue run instead of writing an error.
  • - Introduces separate in_process_media and in_process_thumbnail database fields for the media and thumbnail handlers to avoid interfering with the main staging creation process which uses the existing in_process field.
5.4.11 18 March 2026 >=6.7.0.0 < 6.8.0.0
  • - Improvement: Removed unreliable cache clearing via shell_exec at the end of staging creation. Instead, var/cache is now automatically added to the excluded directories of all existing staging records on plugin install and update, so the staging system always starts with a fresh cache generated from the correct staging configuration.
5.4.10 17 March 2026 >=6.7.0.0 < 6.8.0.0
  • - Fixes the "SHOP-ID changed" modal appearing on the staging system after login by updating all fingerprints (installation_path, sales_channel_domain_urls) in the shop ID configuration during staging creation.
  • - Added automatic cache clearing on the staging system at the end of the staging creation process.
5.4.9 11 March 2026 >=6.7.0.0 < 6.8.0.0
  • - Adds a new `in_process` flag to the staging entity to track whether a queue process has completed its main operation before dispatching the next message.
  • - Implements a `dispatchWithConnectionCheck()` method in `DatabaseService` that verifies the database connection before dispatching a message and automatically reconnects if the connection was lost.
  • - Applies the new retry mechanism to all staging queue handlers so that if the database connection is lost after a long-running operation, the next message is automatically re-dispatched on the next queue run instead of writing an error.
5.4.8 19 February 2026 >=6.7.0.0 < 6.8.0.0
  • - Optimizes COMPOSER_HOME path for the staging system in the configuration.
5.4.7 10 February 2026 >=6.7.0.0 < 6.8.0.0
  • - Optimizes creating of the staging system.
5.4.6 3 February 2026 >=6.7.0.0 < 6.8.0.0
  • - Fixes database permission issues during staging user generation by using the correct database connection.
5.4.5 3 February 2026 >=6.7.0.0 < 6.8.0.0
  • - Optimized file operations by adding native PHP fallbacks for environments where shell_exec is disabled, while maintaining performance on systems where it is available.
5.4.4 31 January 2026 >=6.7.0.0 < 6.8.0.0
  • - Fixes the issue with excluded directories in the files folder.
5.4.3 30 January 2026 >=6.7.0.0 < 6.8.0.0
  • - Optimized database validation for staging creation.
5.4.2 26 January 2026 >=6.7.0.0 < 6.8.0.0
  • - Optimizes copying of system files during staging creation.
5.4.1 23 January 2026 >=6.7.0.0 < 6.8.0.0
  • - Optimized database URL parsing when no port is specified.
5.4.0 21 January 2026 >=6.7.0.0 < 6.8.0.0
  • - Added option to ignore Shopware Migration Assistant database tables during staging creation.
5.3.8 16 January 2026 >=6.7.0.0 < 6.8.0.0
  • - Fixes staging status display issue in storefront and administration.
5.3.7 7 January 2026 >=6.7.0.0 < 6.8.0.0
  • - Disabled indexing via robots.txt if it is a staging system.
5.3.6 17 December 2025 >=6.7.0.0 < 6.8.0.0
  • - Fixes the issue on entering the same database name from the live system for the staging system.
5.3.5 17 December 2025 >=6.7.0.0 < 6.8.0.0
  • - Fixes the issue on incorrect permissions for the staging system.
5.3.4 16 December 2025 >=6.7.0.0 < 6.8.0.0
  • - Fixes the issue on clearing Elasticsearch indexes on creating new staging system and on deleting the staging system.
5.3.3 15 December 2025 >=6.7.0.0 < 6.8.0.0
  • - Fixes potential issues with a plugin update when the update didn’t work properly before.
5.3.2 15 December 2025 >=6.7.0.0 < 6.8.0.0
  • - Fixes potential issues with a plugin update across different server environments.
5.3.1 9 December 2025 >=6.7.0.0 < 6.8.0.0
  • - Implemented staging user role selection during staging site creation.
5.3.0 1 December 2025 >=6.7.0.0 < 6.8.0.0
  • - Added functionality to automatically create admin users during staging system creation.
5.1.6 27 November 2025 >=6.7.0.0 < 6.8.0.0
  • - Optimizes creating and updating of the staging system.
5.1.5 28 October 2025 >=6.7.0.0 < 6.8.0.0
  • - Fixes the issue on preparing .env files which contains values with space for the staging system.
5.1.4 15 October 2025 >=6.7.0.0 < 6.8.0.0
  • - Fixes the issue with excluded directories.
5.1.3 1 October 2025 >=6.7.0.0 < 6.8.0.0
  • - Optimizes changing of specific tables.
5.1.2 30 September 2025 >=6.7.0.0 < 6.8.0.0
  • - Fixes issue copying files to the staging system.
  • - Optimizes reindexing of Elasticsearch indexes for the staging system.
5.1.1 22 September 2025 >=6.7.0.0 < 6.8.0.0
  • - Fixes issue on adding exclude directory field to the database.
5.1.0 19 September 2025 >=6.7.0.0 < 6.8.0.0
  • - Added configuration for excluding directories when creating the staging.
5.0.4 27 August 2025 >=6.7.0.0 < 6.8.0.0
  • - Optimizes changing of files permissions for the staging system.
5.0.3 30 July 2025 >=6.7.0.0 < 6.8.0.0
  • - Fixed icon compatibility with other plugins.
5.0.2 11 July 2025 >=6.7.0.0 < 6.8.0.0
  • - Improved plugin compatibility with Shopware 6.7.
5.0.1 3 July 2025 >=6.7.0.0 < 6.8.0.0
  • - Improved plugin compatibility with Shopware 6.7.
5.0.0 7 May 2025 >=6.7.0.0 < 6.8.0.0
  • - Compatibility with Shopware 6.7.
  • - Support for the following languages: de-DE, en-GB, nl-NL, fr-FR, es-ES, fi-FI, nn-NO, sv-SE, cs-CZ, pt-PT, tr-TR, da-DK, it-IT, pl-PL, bs-BA
4.11.2 10 August 2026 >=6.6.0.0 < 6.7.0.0
  • - Fixed: The administration template of the plugin no longer replaces the template of the Shopware Administration, so template extensions of other plugins are not skipped any more.
  • - Fixed: Whether the additional feature "Staging on an external server" is available is now determined by the server instead of a value injected into the Administration.
4.11.1 6 August 2026 >=6.6.0.0 < 6.7.0.0
  • - Fixed: Creating the staging system could fail with "mkdir(): File exists" when the shop uses a symlinked var/cache or var/log directory (e.g. shared-directory deployments).
4.11.0 5 August 2026 >=6.6.0.0 < 6.7.0.0
  • - The additional feature "Staging on an external server" is now presented in an own card at the top of the staging system with a description of the feature and the purchase instructions.
  • - Fixed: A missing Shopware account login is now reported as such instead of a general error message.
4.10.0 5 August 2026 >=6.6.0.0 < 6.7.0.0
  • - Added #32627: Staging system on an external server via SSH/SFTP, in the CS version with the in-app purchase "Staging on an external server".
  • - Added #38174: Own APP URL (custom domain/subdomain) for the staging system instead of the automatically generated URL.
  • - Added: Configurable staging domains per sales channel domain.
  • - Fixed: File permissions are applied again (the chmod command was built without a space, so it was never executed).
  • - Fixed: Shell commands for deleting and linking the staging directory are now escaped correctly.
  • - Fixed: Corrected the names of the API routes.
4.9.2 15 July 2026 >=6.6.0.0 < 6.7.0.0
  • - Fixed: With password protection enabled, the staging Administration kept prompting for the password and reloaded endlessly, while the storefront worked. The password prompt is now only shown for actual page loads, so the Administration and its background requests are no longer blocked.
4.9.1 13 July 2026 >=6.6.0.0 < 6.7.0.0
  • - Fixed: Reconnect database connection after long-running public/media/vendor/rest file copy operations (CopyPublicFiles, CopyMediaFolder, CopyVendorFiles, CopyFileSystem) to prevent "MySQL server has gone away" / "client was disconnected by the server because of inactivity" errors during staging creation on shops with a large file count.
4.9.0 1 July 2026 >=6.6.0.0 < 6.7.0.0
  • - Added HTTP Basic Authentication password protection for staging environments.
  • - Password is hashed with bcrypt before storage; Symfony toolbar is hidden when protection is enabled.
4.8.3 17 June 2026 >=6.6.0.0 < 6.7.0.0
  • - Fixed: Replaced direct `require_once vendor/autoload.php` with PSR-4 namespace registration on the existing Composer ClassLoader to avoid registering a second autoloader, which caused a warning in Frosh Tools ("2 autoloaders registered: acris/staging").
4.8.2 15 June 2026 >=6.6.0.0 < 6.7.0.0
  • - The profiler configuration file is no longer created if the web-profiler-bundle is not installed.
4.8.1 11 June 2026 >=6.6.0.0 < 6.7.0.0
  • - Renamed profiler configuration file for staging systems to ensure correct loading order.
4.8.0 3 June 2026 >=6.6.0.0 < 6.7.0.0
  • - Added option to disable Symfony toolbar for dev mode staging systems.
4.7.9 1 June 2026 >=6.6.0.0 < 6.7.0.0
  • - Improved copying shopware files.
4.7.8 28 May 2026 >=6.6.0.0 < 6.7.0.0
  • - Adds the database tables of the ACRIS stock notification plugin to the list of unnecessary tables so they are ignored during the staging database migration.
4.7.7 27 May 2026 >=6.6.0.0 < 6.7.0.0
  • - Fixed: Reset copyMediaFolder and copyThumbnailFolder status to null before dispatching queue messages to prevent stuck running state on new staging creation attempt.
4.7.6 8 May 2026 >=6.6.0.0 < 6.7.0.0
  • - Fixed: Reconnect database connection after long-running thumbnail folder copy operation to prevent "MySQL server has gone away" error during staging creation.
4.7.5 5 May 2026 >=6.6.0.0 < 6.7.0.0
  • - Fixed: SHOPWARE_ES_THROW_EXCEPTION is automatically set to 0 in staging .env files to prevent Elasticsearch errors during Shopware updates
  • - Behoben: SHOPWARE_ES_THROW_EXCEPTION wird in den Staging .env-Dateien automatisch auf 0 gesetzt, um Elasticsearch-Fehler bei Shopware-Updates zu verhindern
4.7.4 2 April 2026 >=6.6.0.0 < 6.7.0.0
  • - Fixes the "Domain change detected" modal appearing on the staging system after login by updating all shopIdV2 fingerprints (app_url, installation_path, sales_channel_domain_urls) in the shop ID configuration during staging creation.
  • - Removes the cache clearing step during staging creation so that the source system cache is no longer wiped during the process and the staging system generates its own fresh cache independently.
  • - Adds var/cache as a default excluded directory for new staging configurations to ensure the staging system always starts with a fresh cache.
  • - Automatically adds var/cache to the excluded directories of all existing staging records on plugin install and update.
4.7.3 19 February 2026 >=6.6.0.0 < 6.7.0.0
  • - Optimizes COMPOSER_HOME path for the staging system in the configuration.
4.7.2 10 February 2026 >=6.6.0.0 < 6.7.0.0
  • - Improves plugin compatibility.
4.7.1 23 January 2026 >=6.6.0.0 < 6.7.0.0
  • - Optimized database URL parsing when no port is specified.
4.7.0 21 January 2026 >=6.6.0.0 < 6.7.0.0
  • - Added option to ignore Shopware Migration Assistant database tables during staging creation.
4.6.6 17 December 2025 >=6.6.0.0 < 6.7.0.0
  • - Fixes the issue on creating and updating the staging system.
4.6.5 17 December 2025 >=6.6.0.0 < 6.7.0.0
  • - Fixes the issue on incorrect permissions for the staging system.
4.6.4 16 December 2025 >=6.6.0.0 < 6.7.0.0
  • - Fixes the issue on clearing Elasticsearch indexes on creating new staging system and on deleting the staging system.
4.6.3 28 October 2025 >=6.6.0.0 < 6.7.0.0
  • - Fixes the issue on preparing .env files which contains values with space for the staging system.
4.6.2 30 September 2025 >=6.6.0.0 < 6.7.0.0
  • - Fixes issue copying files to the staging system.
  • - Optimizes reindexing of Elasticsearch indexes for the staging system.
4.6.1 22 September 2025 >=6.6.0.0 < 6.7.0.0
  • - Fixes issue on adding exclude directory field to the database.
4.6.0 19 September 2025 >=6.6.0.0 < 6.7.0.0
  • - Added configuration for excluding directories when creating the staging.
4.5.3 27 August 2025 >=6.6.0.0 < 6.7.0.0
  • - Optimizes changing of files permissions for the staging system.
4.5.2 18 March 2025 >=6.6.0.0 < 6.7.0.0
  • - Optimizes changing of the public files permissions.
4.5.1 6 March 2025 >=6.6.0.0 < 6.7.0.0
  • - Fixes message loading for staging system status in the admin.
4.5.0 6 March 2025 >=6.6.0.0 < 6.7.0.0
  • - Fixes the permission issue on the staging system.
  • - Fixes the issue with Elasticsearch index.
  • - Rebuilds Elasticsearch indexes for the staging system if the Elasticsearch is active.
4.4.16 25 February 2025 >=6.6.0.0 < 6.7.0.0
  • - Fixes the cache issue during the creation of the staging system.
4.4.15 31 January 2025 >=6.6.0.0 < 6.7.0.0
  • - Optimization in the creation of the staging system in connection with plugins that are inserted into the static-plugins folder and installed via Composer.
4.4.14 28 January 2025 >=6.6.0.0 < 6.7.0.0
  • - Optimizes copying of the public files to the staging system.
4.4.13 24 January 2025 >=6.6.0.0 < 6.7.0.0
  • - Fixes the issue on creating the staging system.
4.4.12 8 January 2025 >=6.6.0.0 < 6.7.0.0
  • - Customisation of texts in Admin.
4.4.11 6 December 2024 >=6.6.0.0 < 6.7.0.0
  • - Optimizes file paths of the import / export processes on the staging system.
4.4.10 25 November 2024 >=6.6.0.0 < 6.7.0.0
  • - Fixes the issue on creating the staging system.
4.4.9 14 November 2024 >=6.6.0.0 < 6.7.0.0
  • - Optimizes creating of the staging system.
4.4.8 11 November 2024 >=6.6.0.0 < 6.7.0.0
  • - Optimizes staging access data.
4.4.7 23 October 2024 >=6.6.0.0 < 6.7.0.0
  • - Optimizes adaptations of the staging database after the database import.
4.4.6 16 October 2024 >=6.6.0.0 < 6.7.0.0
  • - Fixes the issue with preparing the config file.
4.4.5 30 September 2024 >=6.6.0.0 < 6.7.0.0
  • - Fixes the issue on the overwriting of variables in env.local file on the staging system.
4.4.4 30 September 2024 >=6.6.0.0 < 6.7.0.0
  • - Optimizes loading of the env data.
4.4.3 30 September 2024 >=6.6.0.0 < 6.7.0.0
  • - Fixes the issue on overwriting the APP_URL variable in .env.local file on the Shopware update of the staging system.
4.4.2 26 September 2024 >=6.6.0.0 < 6.7.0.0
  • - Fixes a possible problem where a licence warning occurred in the staging system after a shop update.
4.4.1 24 September 2024 >=6.6.0.0 < 6.7.0.0
  • - Bugfix added check if staging entity exits to prevent error.
4.4.0 20 September 2024 >=6.6.0.0 < 6.7.0.0
  • - Added option to set staging to dev mode after creation.
4.3.2 18 September 2024 >=6.6.0.0 < 6.7.0.0
  • - Fixes the issue on removing variables from env.local on the Shopware update.
4.3.1 17 September 2024 >=6.6.0.0 < 6.7.0.0
  • - Fix the issue with staging prefix in the package configurations.
4.3.0 16 September 2024 >=6.6.0.0 < 6.7.0.0
  • - Added field to insert internal comment.
4.2.2 9 August 2024 >=6.6.0.0 < 6.7.0.0
  • - Generates new configuration shopId value for the staging system.
4.2.1 5 August 2024 >=6.6.0.0 < 6.7.0.0
  • - Fixes a problem when importing the staging database.
4.2.0 1 August 2024 >=6.6.0.0 < 6.7.0.0
  • - Optimizes database export and import processes.
4.1.0 26 July 2024 >=6.6.0.0 < 6.7.0.0
  • - Adds force cancel button.
4.0.11 1 July 2024 >=6.6.0.0 < 6.7.0.0
  • - Adds validation on creating staging tables in the database.
4.0.10 1 July 2024 >=6.6.0.0 < 6.7.0.0
  • - Fixes the issue on creating staging tables in the database.
4.0.9 21 June 2024 >=6.6.0.0 < 6.7.0.0
  • - Improves plugin compatibility.
4.0.8 17 June 2024 >=6.6.0.0 < 6.7.0.0
  • - Optimizes database import via message queue.
4.0.7 27 May 2024 >=6.6.0.0 < 6.7.0.0
  • - Fixes the issue with the 'DEFINER' on importing the database to the staging system.
4.0.6 21 May 2024 >=6.6.0.0 < 6.7.0.0
  • - Improves creating of staging system without message queue in the admin.
4.0.5 7 May 2024 >=6.6.0.0 < 6.7.0.0
  • - Fixes the issue with composer update.
4.0.4 25 April 2024 >=6.6.0.0 < 6.7.0.0
  • - Optimizes copying of file system files.
4.0.3 22 April 2024 >=6.6.0.0 < 6.7.0.0
  • - Improves plugin compatibility.
4.0.2 8 April 2024 >=6.6.0.0 < 6.7.0.0
  • - Optimizes copying of file system files.
4.0.1 25 March 2024 >=6.6.0.0 < 6.7.0.0
  • - Changed Pipeline
4.0.0 19 March 2024 >=6.6.0.0 < 6.7.0.0
  • - Compatibility with Shopware 6.6.
3.7.1 25 February 2025 >=6.5.7.0 < 6.6.0.0
  • - Fixes the cache issue during the creation of the staging system.
3.7.0 4 February 2025 >=6.5.7.0 < 6.6.0.0
  • - Improves plugin compatibility.
3.6.17 11 February 2026 >=6.5.0.0 <6.6.0.0
  • - Fixes the issue "unlink(): Argument #1 ($filename) must be of type string, false given" during staging system recreation by improving path resolution in file operations.
3.6.16 3 February 2026 >=6.5.0.0 <6.6.0.0
  • - Optimized file operations by adding native PHP fallbacks for environments where shell_exec is disabled, while maintaining performance on systems where it is available.
3.6.15 4 February 2025 >=6.5.0.0 <6.6.0.0
  • - Improves plugin compatibility.
3.6.14 31 January 2025 >=6.5.0.0 <6.6.0.0
  • - Optimization in the creation of the staging system in connection with plugins that are inserted into the static-plugins folder and installed via Composer.
3.6.13 28 January 2025 >=6.5.0.0 <6.6.0.0
  • - Optimizes copying of the public files to the staging system.
3.6.12 28 January 2025 >=6.5.0.0 <6.6.0.0
  • - Fixes the issue on creating the staging system.
3.6.11 6 December 2024 >=6.5.0.0 <6.6.0.0
  • - Optimizes file paths of the import / export processes on the staging system.
3.6.10 16 October 2024 >=6.5.0.0 <6.6.0.0
  • - Fixes the issue with preparing the config file.
3.6.9 30 September 2024 >=6.5.0.0 <6.6.0.0
  • - Fixes the issue on the overwriting of variables in env.local file on the staging system.
3.6.8 30 September 2024 >=6.5.0.0 <6.6.0.0
  • - Optimizes loading of the env data.
3.6.7 30 September 2024 >=6.5.0.0 <6.6.0.0
  • - Fixes a issue on overwriting the APP_URL variable in .env.local file on the Shopware update of the staging system.
3.6.6 26 September 2024 >=6.5.0.0 <6.6.0.0
  • - Fixes a possible problem where a licence warning occurred in the staging system after a shop update.
3.6.5 24 September 2024 >=6.5.0.0 <6.6.0.0
  • - Bugfix added check if staging entity exits to prevent error.
3.6.4 18 September 2024 >=6.5.0.0 <6.6.0.0
  • - Fixes the issue on removing variables from env.local on the Shopware update.
3.6.3 17 September 2024 >=6.5.0.0 <6.6.0.0
  • - Fix the issue with staging prefix in the package configurations.
3.6.2 9 August 2024 >=6.5.0.0 <6.6.0.0
  • - Generates new configuration shopId value for the staging system.
3.6.1 5 August 2024 >=6.5.0.0 <6.6.0.0
  • - Fixes a problem when importing the staging database.
3.6.0 1 August 2024 >=6.5.0.0 <6.6.0.0
  • - Optimizes database export and import processes.
3.5.0 26 July 2024 >=6.5.0.0 <6.6.0.0
  • - Adds force cancel button.
3.4.12 1 July 2024 >=6.5.0.0 <6.6.0.0
  • - Adds validation on creating staging tables in the database.
3.4.11 1 July 2024 >=6.5.0.0 <6.6.0.0
  • - Fixes the issue on creating staging tables in the database.
3.4.10 21 June 2024 >=6.5.0.0 <6.6.0.0
  • - Improves plugin compatibility.
3.4.9 17 June 2024 >=6.5.0.0 <6.6.0.0
  • - Optimizes database import via message queue.
3.4.8 27 May 2024 >=6.5.0.0 <6.6.0.0
  • - Fixes the issue with the 'DEFINER' on importing the database to the staging system.
3.4.7 6 May 2024 >=6.5.0.0 <6.6.0.0
  • - Fixes the issue with composer update.
3.4.6 2 May 2024 >=6.5.0.0 <6.6.0.0
  • - Improves plugin compatibility.
3.4.5 25 April 2024 >=6.5.0.0 < 6.6.0.0
  • - Optimizes copying of file system files.
3.4.4 22 April 2024 >=6.5.0.0
  • - Improves plugin compatibility.
3.4.3 8 April 2024 >=6.5.0.0
  • - Optimizes copying of file system files.
3.4.2 10 March 2024 >=6.5.0.0
  • - Optimizes assigning of permissions for files on the staging system.
3.4.1 4 March 2024 >=6.5.0.0
  • - Optimizes configuration of Shopware yaml file on the staging system.
3.4.0 19 February 2024 >=6.5.0.0
  • - Optimizes executing the staging messages via message queue.
3.3.9 19 February 2024 >=6.5.0.0
  • - Optimizes changing permissions of config/jwt files on the staging system.
3.3.8 18 January 2024 >=6.5.0.0
  • - Optimizes database credential validation.
3.3.7 19 December 2023 >=6.5.0.0
  • - Changed file permissions of config/jwt of staging system
3.3.6 14 December 2023 >=6.5.0.0
  • - Optimizes db adaptions.
3.3.5 14 December 2023 >=6.5.0.0
  • - Improves copying of the files to the staging system.
3.3.4 13 December 2023 >=6.5.0.0
  • - Optimizes copying of the files to the staging system.
3.3.3 4 December 2023 >=6.5.0.0
  • - Optimizes the generating of the symlink.
3.3.2 21 November 2023 >=6.5.0.0
  • - Fixed issue when trying to remove the filesystem
3.3.1 21 November 2023 >=6.5.0.0
  • - Optimized Admin
3.2.4 14 November 2023 >=6.5.0.0
  • - Fixed error when updating from Shopware 6.4 versions.
3.2.3 9 November 2023 >=6.5.0.0
  • - Fixed php error on creating the staging.
3.2.2 9 November 2023 >=6.5.0.0
  • - Optimization of the creation of the symlink for the staging system.
3.2.1 6 November 2023 >=6.5.0.0
  • - Fixed issue with disabling mail sending option not saving in administration.
3.2.0 3 November 2023 >=6.5.0.0
  • - Added option to deactivate mail sending on newly created staging systems.
  • - Added button with link to open the staging admin or storefront in new tab.
  • - Optimised staging Sales Channel IP whitelist if maintenance mode is active.
3.1.13 16 October 2023 >=6.5.0.0
  • - Optimizes copying of the public folder via message queue.
3.1.12 16 October 2023 >=6.5.0.0
  • - Fixes an issue where the URLs for different language shops were generated incorrectly.
3.1.11 18 September 2023 >=6.5.0.0
  • - Improved error handling. From now on, the cause of the error is better documented for more effective troubleshooting.
  • - Improved error display in the Admin.
  • - Improved error display when a directory could not be copied.
3.1.10 13 September 2023 >=6.5.0.0
  • - Fixes an important issue where the staging system could not be created correctly.
3.1.9 31 August 2023 >=6.5.0.0
  • - Fixes a problem where error messages from the creation of the staging system were not correctly recorded in the log.
3.1.8 30 August 2023 >=6.5.0.0
  • - Fixes possible problems when emptying the staging database.
3.1.7 17 August 2023 >=6.5.0.0
  • - The database table contents of the Shopware Flow Builder Delay functionality are immediately no longer copied when creating the staging system.
3.1.6 17 August 2023 >=6.5.0.0
  • - The database tables of the ACRIS plugin "Flow Builder Extension: Time Delay (Minutes, Hours, Days)" are no longer copied when creating the staging system.
3.1.5 16 August 2023 >=6.5.0.0
  • - Optimizes preparing of the local config for the staging system.
3.1.4 16 August 2023 >=6.5.0.0
  • - Optimizes copying of the files from the public folder.
  • - Optimizes adaptation of the data in the database for the staging system.
  • - Optimizes data import to the staging system.
3.1.3 7 August 2023 >=6.5.0.0
  • - Fixes possible problems with the plugin update.
3.1.2 20 June 2023 >=6.5.0.0
  • - Fixed staging freezing during creating process in message queue.
3.1.1 20 June 2023 >=6.5.0.0
  • - Fixed possible error w=in public files copy step.
3.1.0 6 June 2023 >=6.5.0.0
  • - Optimised staging creation in message queue.
  • - Added back possibility to create staging without message queue.
3.0.0 5 May 2023 >=6.5.0.0
  • - Compatibility with Shopware 6.5.
2.6.2 9 August 2024 >=6.4.5.0 <6.5.0.0
  • - Generates new configuration shopId value for the staging system.
2.6.1 5 August 2024 >=6.4.5.0 <6.5.0.0
  • - Fixes a problem when importing the staging database.
2.6.0 1 August 2024 >=6.4.5.0 <6.5.0.0
  • - Optimizes database export and import processes.
2.5.6 21 June 2024 >=6.4.5.0 <6.5.0.0
  • - Improves plugin compatibility.
2.5.5 13 June 2024 >=6.4.5.0 <6.5.0.0
  • - Optimizes database import via message queue.
2.5.4 9 November 2023 >=6.4.5.0
  • - Fixed php error on creating the staging.
2.5.3 31 October 2023 >=6.4.5.0
  • - Optimised opening admin and storefront from the staging detail admin page.
2.5.2 31 October 2023 >=6.4.5.0
  • - Optimised staging IP whitelist if maintenance mode is active.
2.5.1 31 October 2023 >=6.4.5.0
  • - Added button with link to open the staging storefront in new tab.
2.5.0 30 October 2023 >=6.4.5.0
  • - Added option to deactivate mail sending on newly created staging systems.
2.4.9 16 October 2023 >=6.4.5.0
  • - Optimizes copying of the public folder via message queue.
2.4.8 16 October 2023 >=6.4.5.0
  • - Fixes an issue where the URLs for different language shops were generated incorrectly.
2.4.7 13 September 2023 >=6.4.5.0
  • - Fixes an important issue where the staging system could not be created correctly.
2.4.6 11 September 2023 >=6.4.5.0
  • - Fixes a problem where error messages from the creation of the staging system were not correctly recorded in the log.
2.4.5 17 August 2023 >=6.4.5.0
  • - The database tables of the ACRIS plugin "Flow Builder Extension: Time Delay (Minutes, Hours, Days)" are no longer copied when creating the staging system.
2.4.4 16 August 2023 >=6.4.5.0
  • - Optimizes preparing of the local config for the staging system.
2.4.3 16 August 2023 >=6.4.5.0
  • - Optimizes copying of the files from the public folder.
  • - Optimizes adaptation of the data in the database for the staging system.
  • - Optimizes data import to the staging system.
2.4.2 10 July 2023 >=6.4.5.0
  • - Optimizes creating of the staging symlink.
2.4.1 6 June 2023 >=6.4.5.0
  • - Optimised plugin compatibility.
2.4.0 2 June 2023 >=6.4.5.0
  • - Added back the option to create staging system without message queue.
2.3.2 22 May 2023 >=6.4.5.0
  • - Added info texts if copying media or thumbnail folder has not finished yet.
2.3.1 22 May 2023 >=6.4.5.0
  • - Optimised copying media and thumbnail files during staging creation.
2.3.0 28 March 2023 >=6.4.5.0
  • - Added button to cancel the staging creation inside administration configuration page.
2.2.0 27 March 2023 >=6.4.5.0
  • - Added staging creation process logger to administration detail page.
2.1.1 16 March 2023 >=6.4.0.0
  • - Optimised staging creation process.
2.1.0 13 March 2023 >=6.4.0.0
  • - Improved staging creation process in message queue.
2.0.10 15 February 2023 >=6.4.0.0
  • - Change of the plugin name and the manufacturer links.
2.0.9 26 November 2022 >=6.4.0.0
  • - Improves compatibility with 3rd party plugins.
2.0.8 26 November 2022 >=6.4.0.0
  • - Optimized the Mysqldump to dump virtual values correctly.
2.0.7 26 November 2022 >=6.4.0.0
  • - Optimizes staging URL in config repository when creating the staging system.
2.0.6 26 November 2022 >=6.4.0.0
  • - Optimizes plugin image.
  • - Improves compatibility with Shopware >= 6.4.10.0.
  • - Optimizes plugin color in administration.
2.0.5 26 November 2022 >=6.4.0.0
  • - In case of errors, also displays the original error message for better error handling and traceability.
2.0.4 26 November 2022 >=6.4.0.0
  • - Optimization of staging public folder permissions.
2.0.3 26 November 2022 >=6.4.0.0
  • - Optimization of staging display in conjunction with other plugins.
2.0.2 26 November 2022 >=6.4.0.0
  • - Changed the status display of the Staging system.
2.0.1 26 November 2022 >=6.4.0.0
  • - Increases compatibility with other plugins.
2.0.0 26 November 2022 >=6.4.0.0
  • - Improved compatibility with Shopware 6.4*.
1.4.3 26 November 2022 >=6.3.0.0
  • - Increases compatibility with other plugins.
1.4.2 26 November 2022 >=6.3.0.0
  • - Add validation on creating the staging system.
Reviews
24 reviews
23
0
0
1
0
Write review

Tolles Plugin für Staging und ausgezeichneter Support

· 21 May 2026

Mittlerweile möchte ich das Plugin nicht mehr missen. Das Erstellen und Verwalten von Staging-Umgebungen ist hiermit ein Kinderspiel.
Bei dem ersten Einsatz kam es zwar zu unerklärlichen Fehlern im Bezug auf Bilder, aber das hatte keinerlei Auswirkungen auf den Live-Shop. Der Support kümmerte sich umgehend um das Problem und innerhalb kürzester Zeit war der Fehler behoben und eine aktualisierte Plugin-Version im Store vorhanden.
Auch bei allgemeinen Fragen rund um das Plugin ist der Support zu jeder Zeit hilfsbereit und geduldig. Vielen Dank und weiter so.

Wirklich hilfreiches Plugin

· 3 March 2026

Mir hilft dieses Plugin schon seit einiger Zeit. Damit lassen sich Änderung/updates vorab gut testen. Der Support ist großartig und hilft zuverlässig. Danke!

Super Plugin, super Support!

· 12 February 2026

Der Support ist sehr schnell und hilft einem auch mit älteren Versionen. Unser Problem wurde schnell durch eine aktualisierte Plugin Version gelöst.

Super für Staging Umgebungen

· 23 January 2026

Das Plugin ist super. Klappt alles direkt auf Knopfdruck, wie man es sich wünscht. Bei Fragen ist der Support auch direkt da. Kann ich jedem empfehlen!

Super Plugin & Super Support

· 10 September 2025

-