Having read the uSync 9 documentation about appsettings.json, I'm still not sure how exactly to achieve the above behavior :-) I'm guessing it should be something like this?
what this does is move dictionary to the "Settings" group (so it syncs with doctypes, etc) and sets it so only the Settings group is used for Export on Save (events in umbraco) and shown in the UI (so you can't sync content at all).
uSync appsettings.json handlers
Hi all,
We're running Umbraco 9 with uSync 9 on the following environements:
We'd like to set up uSync to the following behavior:
So all in all: we'd like the import to be one way: never overwrite Content and/or Dictionary items.
On some of our Umbraco 8 solutions, we have added the following config:
Having read the uSync 9 documentation about appsettings.json, I'm still not sure how exactly to achieve the above behavior :-) I'm guessing it should be something like this?
Thanks a lot for your help :-)
All the best,
Bo
Hi,
Yes, almost.
As most of the settings are default, you can omit them. then you only need the setting for the dictionaryHandler.
Its lowercase "dictionaryHandler" and there is an extra "settings" in there for the OneWay.
Thanks a lot, Kevin :-) Greatly appreciated!
So if we want to disable the Content handler entirely, we can do this?
In theory , (not 100% sure that works in the latest release candidate)
but it is easier to add it to DisabledHandlers - in the sets config.
In a perfect world (and we are working through this setup for final release)
you would want to move dictionaryHandler to the Settings group, and then disable, content as a group (so content, media, etc.)
this would do it but it doesn't work just yet - this will be work in rc004
what this does is move dictionary to the "Settings" group (so it syncs with doctypes, etc) and sets it so only the Settings group is used for Export on Save (events in umbraco) and shown in the UI (so you can't sync content at all).
Hi Kevin,
Ah, of course :-) It makes sense to move them to the
DisabledHandlers
array. Thanks!I'll make sure to keep an eye on the documentation to see if anything has changed for the final release.
Thanks a lot for your help :-)
is working on a reply...