The usync underneath is installed fresh from dependency (all the .740 versions)
I took a snapshot on my machine synced over VC with another team member and applied the snapshot, all properties updated but nothing was placed in the folders.
Just realised though that he didn't have the folders before applying the snapshot... so they are being created just not populated!
Some of the content types existed before the snapshot and were moved into folders as part of the snapshot if that makes much difference.
Great work on the Snapshots module by the way, we are seeing a lot of promise in using this with multiple team members instead of the normal usync where the def files can conflict.
Yeah I was assuming something wrong about Container folders and internal IDs - I've changed the way that works now, and pushed a new version of uSync.Core out.
If you are using nuget you will just need to update the uSync.Core package to 5.3.1.740
I've also done a minor update to the core usync, to handle the renames & deletes of any containers a bit better. so you probably want to update that too.
Whats the deal with usync vs usnc.backoffice Kevin. Are they the same? Versions seem to line up but only one has the latest patch you mention (which is not the package snapshots depends on)
yeah thats one of the things that annoys me about nuget :)
nothing has changed in snapshots, it works with all versions, but your right if the config of nuget can mean you don't get the latest version when you update :(
I've put a new version of snapshots out, with a higher dependency.
No support for content type folders
Hi,
Just noticed (using snapshots actually, but presume usync standard is the same) that there is no folder support as per the latest release of Umbraco
This is a really good feature so would be good to be able to replicate the functionality over teams and environments.
Thanks
Hi
Content type folders should be supported in the latest version, can you give me a bit of info on what's happening?
(also are you using the latest version of uSync underneath snapshots?)
Kevin
The usync underneath is installed fresh from dependency (all the .740 versions)
I took a snapshot on my machine synced over VC with another team member and applied the snapshot, all properties updated but nothing was placed in the folders.
Just realised though that he didn't have the folders before applying the snapshot... so they are being created just not populated!
Some of the content types existed before the snapshot and were moved into folders as part of the snapshot if that makes much difference.
Great work on the Snapshots module by the way, we are seeing a lot of promise in using this with multiple team members instead of the normal usync where the def files can conflict.
Thanks
Carl
yeah, missed a bit :(
i'll go off and workout what's gone wrong .
Hi
Yeah I was assuming something wrong about Container folders and internal IDs - I've changed the way that works now, and pushed a new version of uSync.Core out.
If you are using nuget you will just need to update the uSync.Core package to 5.3.1.740
Kevin
Hi Kevin.
Thanks for this. I'll update and let you know if there are any issue.
Cool,
I've also done a minor update to the core usync, to handle the renames & deletes of any containers a bit better. so you probably want to update that too.
Kevin
Hi,
Whats the deal with usync vs usnc.backoffice Kevin. Are they the same? Versions seem to line up but only one has the latest patch you mention (which is not the package snapshots depends on)
Thanks
Carl
yeah its a bit historical but - they "should" be the same -
i just forgot one (done now)
Thanks Kevin.
Just as one more question, should the snapshots dependency be updated to the new version too?
Would make it easier for me (and others?) as I can then just update one dependency in a base project.
Thanks
yeah thats one of the things that annoys me about nuget :)
nothing has changed in snapshots, it works with all versions, but your right if the config of nuget can mean you don't get the latest version when you update :(
I've put a new version of snapshots out, with a higher dependency.
It can be annoying you're right,
Feels like it should be standard to upgrade dependencies independent of parents unless you specify a "max version" or siomilar
Thanks
is working on a reply...