I'm currently trying to move all the media from an Umbraco 4.7.0 environment(running Courier 2.7.8.35.v4.zip) to an Umbraco 6.1.6 environment(running Courier 2.7.8.15.v6.zip).
The folders get created under /media and the physical images get moved across correctly. The Umbraco items are also created in the Media section. However, none of the Image properties are set. UmbracoFile is empty, and after looking in the database it's empty in there as well.
The Courier logs show no errors at all - just normal transfers going through. The umbracoLog table doesn't contain any errors that could shed some light on this.
Any deploy is a 2 step process, so step 1 is packaging everything, and step 2 is to unpack them. So we would need to look at both steps to figure out where things went wrong.
So for packaging, first have a look in the folder containing all your packaged assets, you should have a /resources folder which should contain all your media folders and files, secondly, have a look in the /revision/mediaproperties folder and look at a .courier file to see what data it contains, it should list out all a media items property data - do you see the data there?
If these 2 things looks okey, then the problem might be with the extraction, but one step at a time :)
Just checked - the .courier file seems to contain all the data, including the media item property data. The packaged assets are there too. As far as I can tell, the packaging seems to be working fine. :)
I'm trying to transfer the whole media section from the v4 site to the v6 site. The v6 site started off with a completely empty media section. I did a Courier transfer to it from the v4 site.
The files and folder structure got created on the file system for the v6 site. The items got created in the media section for the v6 site as well, in Umbraco. However, none of the properties actually got set. There's no matching between the files on disk, and the items in Umbraco.
hmmm, based on your description, it all seems to be in order, any chance you could zip that revision folder, and send me a link to it? [email protected] ?
No luck I'm afraid. I deployed the files from the second zip file to the version 4 site, and tried transferring again, but the same thing happens - the media items have no property set in Umbraco.
I'll try uninstalling Courier and reinstalling the package using the first zip file, to see if that makes any difference.
I downloaded the patched v6 install you had in the nightlies folder as well, and installed that to the v6 website. Still getting the same issue when doing a transfer - all the media item properties in Umbraco are empty.
Make sure you clear /app_data/courier on both instances - then retry, if no success, repackage and try sending me the same set of files as the last time.
Some good news and some bad news :) The files got transferred ok, but it messed up the file structure - on the source, the structure was parent folder/folder 1/ image 1, whereas on the destination I have a parent folder, a folder 1, and image1 is outside of either folder.
No, that last issue is because of a default setting in /config/courier.config under media which doesnt force parent nodes when you transfer, if you transfer again, things should fall into place automatically, but you can also change the setting in courier.config:
And the problem is, every time at first time the file hiararchy is being missed (all media items are being stored under root node in media section) and when I re-courier same nodes, they get back under their parent.
Media not transferring correctly
I'm currently trying to move all the media from an Umbraco 4.7.0 environment(running Courier 2.7.8.35.v4.zip) to an Umbraco 6.1.6 environment(running Courier 2.7.8.15.v6.zip).
The folders get created under /media and the physical images get moved across correctly. The Umbraco items are also created in the Media section. However, none of the Image properties are set. UmbracoFile is empty, and after looking in the database it's empty in there as well.
The Courier logs show no errors at all - just normal transfers going through. The umbracoLog table doesn't contain any errors that could shed some light on this.
Any ideas? :)
Hi Andrei
Any deploy is a 2 step process, so step 1 is packaging everything, and step 2 is to unpack them. So we would need to look at both steps to figure out where things went wrong.
So for packaging, first have a look in the folder containing all your packaged assets, you should have a /resources folder which should contain all your media folders and files, secondly, have a look in the /revision/mediaproperties folder and look at a .courier file to see what data it contains, it should list out all a media items property data - do you see the data there?
If these 2 things looks okey, then the problem might be with the extraction, but one step at a time :)
Hey Per,
Just checked - the .courier file seems to contain all the data, including the media item property data. The packaged assets are there too. As far as I can tell, the packaging seems to be working fine. :)
Weird, and the media items are all new? you arent just updating exisiting ones?
I'm trying to transfer the whole media section from the v4 site to the v6 site. The v6 site started off with a completely empty media section. I did a Courier transfer to it from the v4 site.
The files and folder structure got created on the file system for the v6 site. The items got created in the media section for the v6 site as well, in Umbraco. However, none of the properties actually got set. There's no matching between the files on disk, and the items in Umbraco.
hmmm, based on your description, it all seems to be in order, any chance you could zip that revision folder, and send me a link to it? [email protected] ?
Hi Per,
Has that helped shed any light on the issue?
Thank you.
Hi Andrei
Found the reason why it doesn't work. There is a small schema difference between v4 and v6 datalayer which makes the import fail, applying a patch now
This is btw only an issue with exporting from V4 and then importing to v6 later.
Updated the build, you can install it as a package:
http://nightly.umbraco.org/UmbracoCourier/2.7.8/nightly%20builds/Courier_2.7.8.41.v4.zip
Or just by updating the dlls in the /bin with files from this .zip:
http://nightly.umbraco.org/UmbracoCourier/2.7.8/nightly%20builds/Courier_2.7.8.41.hotfix.v4.zip
Hi Per,
No luck I'm afraid. I deployed the files from the second zip file to the version 4 site, and tried transferring again, but the same thing happens - the media items have no property set in Umbraco.
I'll try uninstalling Courier and reinstalling the package using the first zip file, to see if that makes any difference.
No luck with the full reinstall either, I'm afraid.
Is there anything I need to deploy to the v6 site, that I'm missing?
Hi Per,
I downloaded the patched v6 install you had in the nightlies folder as well, and installed that to the v6 website. Still getting the same issue when doing a transfer - all the media item properties in Umbraco are empty.
Hi Andrei
Make sure you clear /app_data/courier on both instances - then retry, if no success, repackage and try sending me the same set of files as the last time.
/Per
Hi Per,
Some good news and some bad news :) The files got transferred ok, but it messed up the file structure - on the source, the structure was parent folder/folder 1/ image 1, whereas on the destination I have a parent folder, a folder 1, and image1 is outside of either folder.
However, there's significant progress! :)
Do you need me to package the files again?
No, that last issue is because of a default setting in /config/courier.config under media which doesnt force parent nodes when you transfer, if you transfer again, things should fall into place automatically, but you can also change the setting in courier.config:
https://github.com/umbraco/Courier/blob/master/Documentation/Architecture/Provider-Configuration.md#media
Set the media provider to include parents, then clear /app_data/courier on both instances, repackage and transfer, then it should work
Hi Per,
I had the same issue as Andrei, and tried your latest suggestion:
And the problem is, every time at first time the file hiararchy is being missed (all media items are being stored under root node in media section) and when I re-courier same nodes, they get back under their parent.
Is it something fixable?
Thanks,
Amir
Hi Per,
Any updates?
is working on a reply...