Transferring Media Dependencies in Umbraco Cloud
# help-with-umbraco
p
Whilst I have been working with Umbraco since v3 I am a complete noob when it comes to Umbraco Cloud and only now dipping my toe! I was of the assumption that transferring content would also transfer all dependent resources such as media, however, it appears that is not the case? Am I correct? Having to transfer media in a separate workflow is far from ideal and seems (to me) to remove some of the benefit of the Cloud workflow.
s
It should transfer all media that is picked in media pickers
If you want to transfer everything from the Media Library, you should be able to right-click on the Media root and select
Queue for Transfer
. You should then be able to run the queue from the Workspaces dashboard.
p
Hmm, that's not what I was told by support. > Since there is no media on staging, and you haven't pushed it there first, it doesn't work. > you need to push the media first
We have yet to successfully transfer content between environments due to problems that keep cropping up so have not been off to a good start.
s
I have never experienced media not to be transferred if it was picked in a media picker on a content node
That would be news to me, if that has changed. But... I haven't used cloud for a while
p
Does that also apply to content in BlockLists?
s
It should - But maybe you discovered a bug in Deploy
p
I've had multiple problems with deploy so far 😦
It's come a long way since Umbraco Courier for sure but still yet to be convinced it is going to work for this project 🤞
s
Try running it by support - I am sure they can give a clear answer on what is going on here 🙂
p
I've raised it again and am awaiting a response but when I previously asked about it I was told that dependent media had to be manually transferred but they agreed with me that it was not ideal and wasn't sure why it had been implemented like that.
s
This means that the selected media item doesn't exist in the source environment (the one you are transferring from). It could be because it has been deleted, without removing the reference from the document that has it picked. Deploy has a config setting for ignoring these: https://docs.umbraco.com/umbraco-deploy/getting-started/deploy-settings#ignorebrokendependenciesbehavior
p
Thanks, yes we discovered this yesterday. This is a site migration from v7 to v13 so we will try and rectify these on the next migration attempt. We change the setting you mention above this morning but the transfer still failed and support are looking into the latest problem which was a Deploy API Exception.
3 Views