You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additional context
Currently on Umbraco 13.5.3 - uSync Publisher v13.1.8.0
Is your feature request related to a problem? Please describe.
We multi-host a bunch of websites on one instance. Our environment is setup so that code development is pushed up through dev/staging/prod as expected. However, on the content side we sync content back down from prod to staging. When we test code updates, we try to keep content in test as close as possible to prod. This is what we use uSync Publisher for (only content and media). So when I run a sync from prod to test it will add and update files, but it doesn't delete anything. Which means I have to go to each individual home node and either pull from prod to test or push to test from prod to have it delete content. This wouldn't be that big of a deal if we only had like 5 sites or something, but we have over 200. So running updates has become a tediously manual process to keep things in sync.
Describe the solution you'd like
What I would like is an option to delete the root home and media nodes if I'm running a full sync from staging. Or an option when I Publish/Push to... or Pull Content/Media... a server to enable that option.
Describe alternatives you've considered
I've looked at the available appsettings and I don't seem to see an option to do so. The closest thing I found was "AllowDeletingOfOrphanedItemsForAllTypes" but that seems to only be Data types and Content types, not the actual content or media itself. I tested enabling this in our dev and test environments even with the option enabled, it only added/updated items.
These are the server settings I use:
For reference - this is how things are structured:
Same in the Media tree
The text was updated successfully, but these errors were encountered:
Good news! - you can do this 🙂 . - it isn't quite documented (needs to be added to the docs!)
Because we want to protect 'normal' operations, this isn't on by default but rather hidden behind a configuration setting. AllowDeletingOfOrphanedItemsFromRoot can be set to true for publish and then what you want should happen.
for example.
"uSync": {
"Publisher": {
"Settings": {
"AllowDeletingOfOrphanedItemsFromRoot": true,
.... your other publisher settings here...
}
}
}
i think it needs to be set on all sides (source and target sites).
Additional context
Currently on Umbraco 13.5.3 - uSync Publisher v13.1.8.0
Is your feature request related to a problem? Please describe.
We multi-host a bunch of websites on one instance. Our environment is setup so that code development is pushed up through dev/staging/prod as expected. However, on the content side we sync content back down from prod to staging. When we test code updates, we try to keep content in test as close as possible to prod. This is what we use uSync Publisher for (only content and media). So when I run a sync from prod to test it will add and update files, but it doesn't delete anything. Which means I have to go to each individual home node and either pull from prod to test or push to test from prod to have it delete content. This wouldn't be that big of a deal if we only had like 5 sites or something, but we have over 200. So running updates has become a tediously manual process to keep things in sync.
Describe the solution you'd like
What I would like is an option to delete the root home and media nodes if I'm running a full sync from staging. Or an option when I Publish/Push to... or Pull Content/Media... a server to enable that option.
Describe alternatives you've considered
I've looked at the available appsettings and I don't seem to see an option to do so. The closest thing I found was "AllowDeletingOfOrphanedItemsForAllTypes" but that seems to only be Data types and Content types, not the actual content or media itself. I tested enabling this in our dev and test environments even with the option enabled, it only added/updated items.
These are the server settings I use:
For reference - this is how things are structured:
Same in the Media tree
The text was updated successfully, but these errors were encountered: