Automatically closed - issue fixed for 2 weeks with no activity.
No doubt core is the root cause, however, the occurrence frequency of the error happened on paragraphs is an outcry for more robustness on the module itself.
If my read of core code is correct, `content_translation_language_fallback_candidates_entity_view_alter` is the core code that assigns default translation handler, so when the core issue as @casey and @Berdir pointed out happens, the default handler fails to assign to paragraphs entity definition. If that's the case, patch in #45 should be the simplest solution without tampering or waiting core to fix. However, the interesting part is comment #52 said the error went back even with the patch applied.
I'm going to verify if patch #45 works for my project. Nonetheless, it's no harm to apply it to the codebase and technically it should help on the core's hook issue at least in some cases, so I'd suggest maintainer to consider including it in the following releases.- 🇮🇹Italy apaderno Brescia, 🇮🇹
HTML tags do not need to be translated: A
<div>
is still a<div>
, whichever language is used for the page.
Translators should not change a HTML tag used in a translatable string, though. They do not know where the HTML markup is used, they could make the full page not correct. Automatically closed - issue fixed for 2 weeks with no activity.