Skip to content
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

[Feature Request] Save field selection per entry #20

Open
joelzerner opened this issue Mar 19, 2019 · 1 comment
Open

[Feature Request] Save field selection per entry #20

joelzerner opened this issue Mar 19, 2019 · 1 comment

Comments

@joelzerner
Copy link

#19

The scenario is as I explained it originally in the mentioned issue, where the master content is all the entries in the main EN site, and the US site has mostly the same content, and there are other languages that have completely different content.

There are some instances where pages are different and shouldn't be synced. Currently, because the field selections aren't saved, it relies on the default settings of the field. In both cases, this leaves room for confusion: if the default is set to not sync, then every time an entry is saved, the user has to remember the turn the sync field on and make the selections there. If the default is set to sync automatically, then there's potential for the user to forget to turn sync off for the page(s) that don't need it and then content will get overwritten.

If the selected values for the Site Sync field were saved and remembered, then this issue could be avoided. The Site Sync field could be tucked away in a tab and only needed to be accessed to set up how an entry syncs in the first instance.

@timkelty
Copy link
Owner

Yep! I originally didn't include this, as it didn't fit our use-case, but it should be pretty easy.

I think it would have to be an option, per-field, though – as many times you'd want it to revert to it's defaults as it does now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants