-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can uSync create and delete dictionary keys (just not update/overwrite existing) #368
Comments
HI At the moment the 'create only' option is the main one, this will not then overwrite the updates but we don't support "delete only" just now, but we will add it to the backlog, to see how hard it is to do. |
Hello @KevinJump, our handler is set like this: I've read the documentation and the options All,Import,Export,Events. Thanks! |
Hi, If the events are still firing despite "ExportOnSave" : being set to none i would restart the site just to check the setting has been loaded. But when in create only mode (when exporting or if the "ExportOnSave" is "on") - the file will still get saved to disk, it just won't get imported - because that is when the create only check is made. Kevin |
thnx for clarifying. Regards |
Hi @KevinJump, Does uSync support "delete only" now, or it's still in the backlog? we have a similar situation that we want just to create and delete but not update. |
Hello
By default the DictionaryHandler is treated as a content handler, so Dictionary items are synced when you sync content.
That’s great for new and deleted dictionary keys, however, unchanged dictionary keys would lose values the content editor has entered as they are ‘updated’.
Looking at the documentation https://usync.jumoo.co.uk/docs/uSync/guides/dictionary the only possible option other than the default content handler way is to allow ‘create only’? Is a Create and Delete Only option/mode possible? (just not update)
This seems to be a follow on from #157
Thanks
Andrew
Using usync 9.2
The text was updated successfully, but these errors were encountered: