We have a problem that Paragraphs fields/entities are translated with TMGMT even if they are only referenced and not really updated via the content type. We have one content type which contains the master data and this is then referenced in other content types. Now if we translate the secondary content types with TMGMT, the master data gets updated which we don't want.
1. Create a custom paragraph type
2. Add that to one content type and use widget Paragraphs on form edit as normal
3. Add that same paragraph type to another content type as a reference field and use select list or check box as widget
4. Create dummy content for both content types and translate the secondary content with TMGMT
5. See the paragraph changed in the original content too
Can we filter the translatable-ness based on the field type or widget type? We'd also be perfectly happy to skip translating this field/paragraph altogether but the field shows as "Always embedded" in TMGMT settings page.
Active
1.15
Core
that's in \Drupal\tmgmt_content\Plugin\tmgmt\Source\ContentEntitySource::getEmbeddableFields(), don't remember right now why we also cover regular entity reference paragraph fields alwaays, open to changing that, just remove 'entity_reference' there.