I'm working on updating a couple of Umbraco 7 websites we are hosting. I'm trying to use uSync.Migrations, and I've been able to transfer most of the settings and content to a temporary Umbraco 10, but I'm now realising that nothing in my content tree deeper than 5 levels is exported by the packer. It's not just one document type; I have the same result in two parts of the tree containing different type. The content nodes are present if I do a regular uSync Export; they are just missing when I make a Pack using Migrations.
I'm not seeing why it's doing this. Is that something that can be changed in the settings?
Thanks Marc. I was already had the filenames as guides, but I'm my project folder wasn't at the root. I manage to do it another way, but I'll keep it in mind for the 2nd site.
uSync.Migrations limited in tree depth?
I'm working on updating a couple of Umbraco 7 websites we are hosting. I'm trying to use uSync.Migrations, and I've been able to transfer most of the settings and content to a temporary Umbraco 10, but I'm now realising that nothing in my content tree deeper than 5 levels is exported by the packer. It's not just one document type; I have the same result in two parts of the tree containing different type. The content nodes are present if I do a regular uSync Export; they are just missing when I make a Pack using Migrations.
I'm not seeing why it's doing this. Is that something that can be changed in the settings?
Hi Antoine
Is it the physical paths to the filenames that are too long 260 chars
I did one that was 7 deep and I had to move my project to c:\src to keep file path short and even then I had to move some images 'up' a folder.
It's also possible to make it export the. Config files as guides instead of filenames.
Regards
Marc
Thanks Marc. I was already had the filenames as guides, but I'm my project folder wasn't at the root. I manage to do it another way, but I'll keep it in mind for the 2nd site.
is working on a reply...