This isn't a problem I need help with, but rather I wanted to draw to light an issue I had in case there is a solution for future version.
uSync (vLatest) was setup to output files using Guids.
I deleted a content type. Later I decided I did need it after all and so created it again. As a result of CD to a server this resulted in a deletion and a creation record for a content type of the same alias. It took me a while to work out why some of my content kept being deleted without any trace.
Perhaps the solution is agreeing that I should be clearing the uSync folder on deployment, however it might make sense that the report detects this edge case up and it triggers a warning?
yeah - i can see what we are missing there, when using names for the files - we run a check at every save (because if you rename we need to know) - but we don't do that for guids (because you can change the name and then the guid stays the same).
what we need to do (and we will put this in for a future release). Is run a simpler check to see if the alias has already been used and change that existing file (which will be where the delete is) into a rename (which essentially gets ignored on the import).
Deletion issue with Guid content types
This isn't a problem I need help with, but rather I wanted to draw to light an issue I had in case there is a solution for future version.
uSync (vLatest) was setup to output files using Guids.
I deleted a content type. Later I decided I did need it after all and so created it again. As a result of CD to a server this resulted in a deletion and a creation record for a content type of the same alias. It took me a while to work out why some of my content kept being deleted without any trace.
Perhaps the solution is agreeing that I should be clearing the uSync folder on deployment, however it might make sense that the report detects this edge case up and it triggers a warning?
Hi David,
yeah - i can see what we are missing there, when using names for the files - we run a check at every save (because if you rename we need to know) - but we don't do that for guids (because you can change the name and then the guid stays the same).
what we need to do (and we will put this in for a future release). Is run a simpler check to see if the alias has already been used and change that existing file (which will be where the delete is) into a rename (which essentially gets ignored on the import).
Raised it as an issue for us to look at: https://github.com/KevinJump/uSync8/issues/216
Hi,
Snuck this fix into the latest uSync release (v8.9)
https://github.com/KevinJump/uSync8/releases/tag/8.9.0
Nice. Thank you
is working on a reply...