Problem/Motivation

The translation configuration should ideally be accessible directly within the paragraph type settings. The current requirement to use the global 'Content language and translation' page is inconvenient for large projects with many different paragraph types.

Issue fork paragraphs-3582423

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

igor mashevskyi created an issue. See original summary.

igor mashevskyi opened merge request !241

igor mashevskyi’s picture

igor mashevskyi commented
Assigned: igor mashevskyi » Unassigned
Status: Active » Needs review

I made a pretty simple improvement, hope it won't take a lot of time to test, and it will be merged soon

yashaswi18’s picture

yashaswi18 commented

I have faced the same issue of having to go to the Content Language and Translation page each time to manage paragraph translation settings.
After reviewing the code changes, this approach looks good to me. With this change, translation settings can now be managed directly from the Paragraph Type edit page, which improves the workflow.
I also verified that translated paragraph content continues to work properly with this implementation.
Note: Field-level translation settings still appear to need to be configured separately where needed, which seems to match current Drupal behavior.
Thank you.