- last update
11 months ago Patch Failed to Apply - π§πͺBelgium tijsdeboeck Antwerp π§πͺ πͺπΊ π
We've used patch #33 to fix asymmetric translations, works perfectly!
- πΊπΈUnited States amaisano Boston
I am using D10, Paragraphs 1.16, TMGMT, and cannot get the accepted job translations for paragraph fields into the node translation when it gets created. Or even on updates.
I've enabled translation on the node's "field_paragraphs" field, AND all the fields for my paragraph types.
I'm using non-patched paragraphs_asymmetric_translation_widgets module, and this patch.
I've also tried patch 122 and 128 on the original Paragraphs Experimental issue for asymmetry, same results.
Is there another step I could be missing? Does this not work with D10? All of the patches applied cleanly.
- last update
8 months ago 103 pass, 10 fail - π©π°Denmark Birk
The patch from #33 β¨ Integration with paragraphs asymmetric translation RTBC almost did it for me.
But if the target translation had less paragraphs than the source, the extra paragraphs wasn't added.I've moved around on some parentheses, so the condition is (OR):
$referenced_entity->id() == $field_item[$property]['#id']
Same entity($item_delta === $delta && !$is_target_type_translatable)
Same delta, and not translatable$is_asymmetric_translation_mode
Is asymmetric paragraph
The last submitted patch, 36: 3134922-36.patch, failed testing. View results β
- Status changed to Needs work
8 months ago 1:34pm 3 November 2023 - π©π°Denmark Birk
After I've been working more with the tmgmt module, I realized my previous assumption about the conditions in
findReferenceEntity()
was wrong (and introduced an error where the first paragraph was chosen for cloning each time).
Sorry if this has caused any confusion!Anyway, I think the problem (in my use case) is the
$entity
passed to thedoSaveTranslations()
function, is not using the jobs source language.I've supplied a patch that sets the entity language in the
saveTranslation()
function. - π§π·Brazil adinancenci
If a corresponding paragraph does not exist in the targeted translation, the strings submitted in the tmgmt form will be lost upon completion.
I modified the patch #39 by @birk to create a paragraph.
I hope what I made here makes sense.