Emails and calls How do I stop test emails and calls to the outside?
A copy knows the same customers, the same apps and the same webhooks as the live shop. So by default the plugin keeps emails and calls of apps and webhooks inside: emails land in the mail archive, calls are blocked and logged, scheduled tasks do not run.
Four ways, "Send nothing" is preselected.
The setting "Mails" sits on the page of the staging environment, in the tab "Protection".
- Send nothing
- No mail leaves the staging environment. Each one only appears in the mail archive.
- Everything to one catch-all address
- Every mail goes to an address you enter there or that comes from the plugin settings. Without an address nothing is delivered.
- Only to released addresses
- Only addresses and domains from the list receive mail, one per line, for a whole domain with a leading at sign such as
@agency.example. - As the live shop (to the real recipients)
- Every mail goes to its real recipients, real customers included.
With the first three, every mail appears in the mail archive. Redirected mails only go to the catch-all address or the released addresses, further recipients are dropped. The plugin puts [STAGING] in front of the subject of a delivered mail, adjustable under "Subject prefix" in the plugin settings, card "Mails", for every staging environment. Copy and blind copy recipients are dropped when redirecting, even if they are released.
Every mail the copy would send.
Every staging environment has the mail archive, in its administration under Extensions › Staging Manager › Mail archive. In the live shop it stays empty, because the live shop catches no mails.
- The list
- Time, subject, "Addressed to" with the original recipients, "Delivered to" and the result: "caught" (to nobody) or "redirected" (to catch-all address or allow list).
- Show
- Opens the mail with sender, recipients and content, as HTML or as text. That way you check mail templates with real, anonymized orders.
- Keeping
- After 30 days the archive clears a mail away bit by bit as new ones arrive. "Empty archive" deletes all of them at once. A new build or a refresh starts with an empty archive.
Apps and webhooks reach nothing real.
While setting up, the plugin separates shop id and apps with an app server from the live shop, so no app server takes the copy for the live shop. Whatever still wants to go out is ruled by "Calls of apps and webhooks":
- Block and log
- Default. No call leaves the staging environment.
- Let through and log
- Calls go out as in the live shop, and each one is in the log.
- As the live shop (without log)
- As in the live shop, without a log.
The log is on the dashboard of the copy, card "Outgoing requests": every call and every mail with time, channel, destination and handling, filterable. It covers Shopware's app and webhook calls; connections other plugins make themselves are not covered; such plugins are switched off for the copy in the tab "Setup".
Tasks, tracking and usage data.
- Switch off scheduled tasks
- On (default): no scheduled task of the live shop runs in the staging environment, so no dunning, no newsletter, no sync with ERP or marketplace. The plugin's scheduled tasks never run in the copy.
- Google Analytics
- Off, unless you choose "As the live shop (reports to its account)". Tracking that a plugin brings along is switched off with that plugin.
- Usage data
- Marked as declined for Shopware while "Mark usage data as declined in staging environments" is on (default). No window asks about it in the copy.
- Cron jobs and workers
- The staging environment has none. If you need a worker there, you set it up yourself.
What shop owners ask about it.
Where do I see the emails of the staging environment?
In its mail archive: in the administration of the staging environment under Extensions › Staging Manager › Mail archive. It shows every mail the copy would send, with subject, recipients and full content, as HTML or as text.
How do I test the email delivery itself?
Choose "Everything to one catch-all address" and enter your own address in the tab "Protection" or in the plugin settings. Every mail of the copy then goes to you, with the subject prefix [STAGING]. On the dashboard of the copy, "Test mail" sends a test mail there.
Does the copy report orders to my ERP or marketplace?
Not through apps and webhooks: "Block and log" (default) keeps every such call inside the staging environment and writes it into its log, and scheduled tasks do not run. Plugins with a connection of their own to the ERP are not covered by this; switch them off for the copy in the tab "Setup".
Do newsletters or dunning letters run in the copy?
No, as long as "Switch off scheduled tasks" is on, which is the default. Then no scheduled task of the live shop runs in the staging environment. The copy has no cron jobs or workers of its own anyway.
More about the plugin
-
Setting up
The assistant in seven steps, the preflight and the first build.
-
What gets copied
Which files and tables come along, what stays empty and how rebuilding, refreshing and tearing down work.
-
Anonymization
The rule set, the replacements per column, the preview and the record of every build.
-
Protection and access
Password page, IP addresses without a password, default user, credentials and maintenance mode.
-
Services and plugins
Search, Redis, queue, reverse proxy and plugins: what the copy shares with the live shop.
-
Differences to the live shop
The comparison shows extensions, settings, content, files and database structure, each with its side.
-
Schedule and automation
Schedule, lifetime with reminder, Flow Builder and console commands.
-
Hosting and server
What gets written on the server, Apache, nginx, an address of its own, database privileges and SFTP.
-
Comparison with the standard
What Shopware does itself with system:setup:staging and what the plugin adds.
-
Pricing
What a staging environment costs, monthly or yearly, and what each plan includes.