You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 13/umbraco-deploy/deployment-workflow/content-transfer.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,12 +32,12 @@ You want to transfer the whole site. You start from the `Home` node and choose t
32
32
{% endhint %}
33
33
7. Click **Queue** to add the content item to the transfer queue.
34
34
35
-

35
+
.png>)
36
36
8. Go to the Deployment dashboard by clicking on the Content section header.
37
37
* You will be able to see which items are currently ready to be transferred - this will include both content and media that you've _queued for transfer_.
38
38
9. Confirm by clicking **Transfer toDevelopment** and monitor the progress of the transfer.
If everything went well, you will see the confirmation screen saying that the transfer has succeeded.
43
43
@@ -67,6 +67,6 @@ This does not include entries submitted via the forms.
67
67
68
68
Sometimes a content transfer might not be possible. For example if you add a new property to the HomePage Document type and you don’t have that property in both environments, you’ll get an error with a hint on how to fix this.
69
69
70
-

70
+
.png>)
71
71
72
72
If you are seeing this type of issue when trying to transfer content, head over to our article about [Schema Mismatch errors](../troubleshooting.md), where you can read about how to resolve the issues.
0 commit comments