Problem/Motivation

We have tons of related issues... there is user confusion when users can hit actions that affect all languages while translating.
Core usually doesn't hide, it puts annotation "all translations" to fields.
This is not enough and our users are not aware of the situation.

Proposed resolution

We want to go one step further as our complexity is way bigger. First we started to hide "add paragraph" and this resulted in better awareness. There is still confusion remaining, because we are not strict.

Recently we added a new API to check if structural / reference / shared changes are allowed:
#2923301: Widget actions hook doesn't have information about translating status

Now we can apply the API use on all the related issues:
#2909416: Hide duplicate action while translating
#2918713: Hide Drag & drop action while translating
#2932334: Hide drag handler while translating
From Paragraphs Collection
#2921158: Hide action "convert to library" when translating

If someone doesn't like this hiding, he can help us to provide this option:
#2924774: Let Editors add/delete/clone paragraphs When [Editing a translation] for already translated node which uses paragraphs field

Remaining tasks

Implement the consistency :-)

User interface changes

API changes

Data model changes

Comments

miro_dietiker created an issue. See original summary.

miro_dietiker’s picture

Issue summary: View changes
miro_dietiker’s picture

We have completed hiding of all shared actions.

Just the tabledrag is remaining, but i'm a bit hesitant to push hard there for now as it breaks core behavior quite a bit. :-)

miro_dietiker’s picture

Everything is done here, thus closing.
Adding a follow-up issue that deals with a bug for untranslatable Paragraph Types.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.