You can copy the content in one environment to another for testing purposes. You can copy:
- From Live to UAT or Integration.
- From UAT to Integration.
The copy operation copies all editor-created content, such as pages and assets, from the Magnolia JCR workspaces source environment. Content from both the author and the public instances is copied to corresponding target instances.
The copy operation does not copy:
- Any administrator-created content in the
- Users, roles and groups defined in the Security app.
- Any light modules deployed in the source environment.
Use this functionality to test a new light module or an updated light module in the Integration environment on the basis of your Live or UAT content.
You can only copy content "backward", that is, from Live to UAT or Integration, or from UAT to Integration. To promote your changes "forward", you must define a release.
Note that all content in the target environment is overridden, except the
usergroups workspaces, during the copy operation.
- In Installed releases click Install an update.
- Click Copy content for testing.
- Select the source environment from which you want to copy content and the target environment the content will be copied to before clicking Next.
- Confirm the consequences of the copy operation and click Copy.
The copy operation begins.
- Click OK. As all actions in the Magnolia cockpit are asynchronous, you can click on OK before the copy is complete: the action will run in the background and a notification will appear once it is complete.
This action appears in the activity log and a notification banner is displayed.
Once you have copied the environment's content to another environment and made the changes or corrections you required, you can define a release to wrap these changes in preparation for installation in the UAT or Live environment.
Note that the release versions of the environments displayed in the Package overview are not affected by the copy operation. Check the activity log instead.
Always avoid hotfixing problems in the Resources app because the changes are not propagated back to your GIT repository.