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

BUG [DataObject] 'Paste only contents here' ignores user language permissions #6033

noemiOetker opened this issue Mar 12, 2020 · 0 comments


Copy link

@noemiOetker noemiOetker commented Mar 12, 2020

Bug Report

A user with specific language permissions can overwrite ALL localized fields data of an existing DataObject by using copy + paste only contents here. The system will ignore the user's language permissions setup and will copy all translations.


Expected behavior

The cloning of a DataObject into another existing one overwrites the localized fields data ONLY for the languages the user has writing permissions for.

Actual behavior

The cloning of a DataObject into another existing one overwrites the localized fields data for ALL languages, independently of the ones the user has writing permissions for.

Steps to reproduce

  1. Create a test user with DataObject writing permissions just for a couple of languages.
  2. As an admin user, create a couple of DataObjects with a localized field for several languages (more than the ones the test user has permissions for).
  3. As the test user, right click on one of the DataObjects, click on "Copy".
  4. As the test user, click on the other DataObject, right click and then select "Paste only contents here".
  5. As an admin user, check that ALL translations for the localized fields have been overwritten in the second DataObject with the data of the first one.


This functionality is either removed (not sure what's its use in the first place) or the user language permissions are checked before executing the action, so only the allowed language translations are overwritten.


This behavior is described here: #6011, but there they just ask for a warning. In my opinion this is a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.