- Issue created by @tgoeg
-
alaindessi →
committed 3f4b3b64 on 1.0.x
Issue #3510873 by tgoeg, bigbabert: Markup lost/literal HTML tags...
-
alaindessi →
committed 3f4b3b64 on 1.0.x
- 🇮🇹Italy bigbabert Milano, Italy
Hi @tgoeg,
thanks for reporting, i did a major re-factor of the code and added in 1.3.4 the fix for that using the above code:
if (isset($sub_widget['#format'])) {
$sub_widget['value']['#format'] = $entity->get($field_name)->format;
}
if (isset($sub_widget['#text_format'])) {
$sub_widget['value']['#text_format'] = $entity->get($field_name)->format;
}Please if you found still issue re-open it.
Best regards
- 🇦🇹Austria tgoeg
Thanks for the quick fix again!
I thought I'd write:
I still see literal HTML tags with 1.3.6-beta1, though they get away once I edit the respective paragraphs. I see them (and the translated strings) as soon as I edit the node, even before editing the paragraphs themselves (all done in preview mode when editing an article).Now I saved the translation with its visible HTML tags and deleted the translation afterwards.
When I add a new translation now, I don't get any HTML tags nor do I get any translation of paragraphs when initially editing the new translation. As soon as I click "edit" on a paragraph, it does get translated and HTML tags are correctly parsed.
So I think this can be considered fixed and there might have been some caching issue from the version before. Just wanted to note this down if its ever relevant for anyone seeing the same.Thanks again!
- 🇮🇹Italy bigbabert Milano, Italy
Hi @tgoeg,
thanks to confirm the fix, the cache issue with previous version of the module was due to the fact that paragraphs was saved during the translation, now only the values in the form are updated.
Best regards