I'm currently on uSync 4 for Umbraco V7.14 and no matter how many times I delete something from the content tree, it always comes back. I'm at my wits end and can't find any solutions to this anywhere. Please help.
I've also noticed uSyncActions doesn't trigger/capture any deletions. Tried configuring backoffice but ran into this issue
With uSync 4 when you delete an item, that removes a file from the uSync folder - so you have to make sure you do a clean copy of the uSync files when putting them in a new site (i.e delete the existing folder then copy over the new one)
What is likely happening is that when you copy over the usync files from one site to another (or via deployment) - that isn't removing the old files, so uSync still finds them to recreate the deleted items.
Although we do run multiple environments with uSync on them, this is actually occurring on the same environment, upon IIS start and/or restart.
Essentially, I’d be deleting pages from the content tree and even empty the trash can. The next time IIS reboots on same environment, all of it appears in the content tree again, usually in unpublished state. (uSync + Content Edition settings is set to auto (first option)
The only possible solution I was able to come across here was regarding uSyncActions and how we have to set it to delete (content and/or media in sync settings)
When I try to add those settings into the cfg file, the entire list of handlers is wiped upon IIS reboot, and nothing gets logged in uSyncActions for any deletes.
Is the solution you’re suggesting is to delete the item in the content tree and go into the uSync folder and delete the corresponding folder manually? Then export all?
Wanted to update that I was able to get the Handlersconfig + DeleteActions set up in my uSyncBackOffice config successfully and now uSyncActions file updates with entries of any items that I deleted from the content tree.
However, it still keeps coming back :( So I checked in History to look at the import report log in Developer->uSync-> History tab and it shows the item being deleted, then imported.
What am I doing wrong? (This is all happening on the same environment).
That looks like the original .config files are still there for the items - so uSync will run through the import it deletes first (so deletes from the usyncactions.config file)
and then it is findig the content again on the disk. (so the orginal ".config" file for the item) and it is importing it.
when you delete an item these files should be deleted from the disk, so either that didn't happen (permissions?) or they where restored from somewhere else (like source control?)
Thank you for explaining the process. After understanding how it works + your last sentence gave me a little epiphany lol. You were right, it was bc of source control.
Once I made the delete in the content tree, the files are removed from folder and doing a git status reflects all the deletes. All that was left was for me to add them all to commit and push the untracked changes into the repo and the next startup of IIS spins up the repo with all the deletions reflected.
uSync keeps restoring deleted items from content tree
Hello,
I'm currently on uSync 4 for Umbraco V7.14 and no matter how many times I delete something from the content tree, it always comes back. I'm at my wits end and can't find any solutions to this anywhere. Please help.
I've also noticed uSyncActions doesn't trigger/capture any deletions. Tried configuring backoffice but ran into this issue
Hi
With uSync 4 when you delete an item, that removes a file from the uSync folder - so you have to make sure you do a clean copy of the uSync files when putting them in a new site (i.e delete the existing folder then copy over the new one)
What is likely happening is that when you copy over the usync files from one site to another (or via deployment) - that isn't removing the old files, so uSync still finds them to recreate the deleted items.
Hi Kevin,
Thank you so much for the quick reply.
Although we do run multiple environments with uSync on them, this is actually occurring on the same environment, upon IIS start and/or restart.
Essentially, I’d be deleting pages from the content tree and even empty the trash can. The next time IIS reboots on same environment, all of it appears in the content tree again, usually in unpublished state. (uSync + Content Edition settings is set to auto (first option)
The only possible solution I was able to come across here was regarding uSyncActions and how we have to set it to delete (content and/or media in sync settings)
When I try to add those settings into the cfg file, the entire list of handlers is wiped upon IIS reboot, and nothing gets logged in uSyncActions for any deletes.
Is the solution you’re suggesting is to delete the item in the content tree and go into the uSync folder and delete the corresponding folder manually? Then export all?
I hope I can figure this out. Thank you
Wanted to update that I was able to get the Handlersconfig + DeleteActions set up in my uSyncBackOffice config successfully and now uSyncActions file updates with entries of any items that I deleted from the content tree.
However, it still keeps coming back :( So I checked in History to look at the import report log in Developer->uSync-> History tab and it shows the item being deleted, then imported.
What am I doing wrong? (This is all happening on the same environment).
HI
That looks like the original .config files are still there for the items - so uSync will run through the import it deletes first (so deletes from the usyncactions.config file)
and then it is findig the content again on the disk. (so the orginal ".config" file for the item) and it is importing it.
when you delete an item these files should be deleted from the disk, so either that didn't happen (permissions?) or they where restored from somewhere else (like source control?)
Hi Kevin,
Thank you for explaining the process. After understanding how it works + your last sentence gave me a little epiphany lol. You were right, it was bc of source control.
Once I made the delete in the content tree, the files are removed from folder and doing a git status reflects all the deletes. All that was left was for me to add them all to commit and push the untracked changes into the repo and the next startup of IIS spins up the repo with all the deletions reflected.
<3 aloha,
Phung D.
is working on a reply...