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

Field value doesn't propagate even if translation is turned off #96

Open
MoritzLost opened this issue Sep 11, 2023 · 0 comments
Open

Field value doesn't propagate even if translation is turned off #96

MoritzLost opened this issue Sep 11, 2023 · 0 comments

Comments

@MoritzLost
Copy link

We're seeing an issue where a Preparse field's value doesn't propagate to other sites, even if the Translation Method is set to Not translatable. This only happens if Parse before save is set to No. If this option is set to Yes, the field values propagate as expected.

Is this expected behaviour or a bug? How is the Parse before save intended to be used?

Steps to reproduce

  1. Create a Preparse field in an installation with at least two sites. Set the field options as described above.
  2. Add the field to a section that is active for at least two sites.
  3. Save an entry in that section in one site. The Preparse field's value will only update in that site, while the other site will still have the old value.
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

1 participant