Manual Inside the staging environment.
When you open the administration of a staging environment, its dashboard shows no list but the copy itself. It is always managed in the live shop it comes from.
What the copy catches and whether it is set up right.
- Head
- Name, the live shop it comes from, address, database, when last built and created. "Manage in the live shop" opens its page in the live shop.
- Mails
- How many mails the mail archive caught and whether mails leave the copy: "contained" or "leaves". With a catch-all address, "Test mail" sends a test mail there.
- Requests
- How many calls were blocked or let through; "To the log" jumps to the list below.
- Self-test
- Checks the installation from the inside when opened: marker of the staging environment, staging mode of Shopware, staging variable, database connection, mail delivery, search engines shut out and the live shop's cache. "Details" explains each check, "Check again" starts it anew.
- Outgoing requests
- The log: every caught call and every mail with time, channel, destination and handling, filterable.
System › Mail archive in the copy.
Every mail the copy would send, with "Time", "Subject", "Addressed to", "Delivered to" and "Result". "Show" displays it as HTML or text, "Empty archive" deletes all. After 30 days the archive clears a mail away bit by bit.
"Environments", "Scheduler" and "Anonymization" only show a short message in the copy, because staging environments, runs and schedules do not exist in it.
Password page, login and lock pages.
- Password page
- "This staging environment is protected with a password. What you do here does not happen in the live shop." Below the field "Password" and "Open".
- Administration login
- If the password page also protects the administration and there is a default user, "As <user name>" appears below the form for everybody who entered the page password.
- Lock pages
- "Staging environment is being prepared" during a run, "Staging environment locked" after an incomplete run, "Staging environment expired" after the expiry date.
What it is all for
The manual says where something sits in the administration. Why it is like that and what it brings day to day is explained on the topic pages.
More on this:Emails and callsProtection and access
More chapters
-
Dashboard and list
Tiles, a card per staging environment, the list with columns, filter and row menu.
-
The page of a staging environment
The eight tabs of a staging environment, every field and what it does.
-
The run window
Confirmation, progress, check results, protocol and settings of a run.
-
Scheduler and anonymization
The scheduler with every schedule and the anonymization rule set.
-
All settings
Every field of the plugin configuration with default and effect.
-
Glossary
Staging environment, test system, run, slice, catch-all address and the other words of the plugin.