Patch #3 works with manual git apply, however, does not work with composer patch because Drupal packaging attaches additional information that causes conflict.
wangshy → created an issue.
Passed test.
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.
Closing it since it seems to be a false alarm
wangshy → created an issue.
Reviewed and tested on the issue fork by @reszli
The idea to alter links to checkbox by javascript is not ideal. It makes the significant front-end update only after the page is fully loaded. In some scenario e.g. slow network or low end, this is not unnoticeable. Checkboxes would be ideal to be separate widget that renders checkbox elements directly.
wangshy → created an issue.
wangshy → created an issue.
Patch attached.
wangshy → created an issue.
#6 patch has some bug that has conflicts in settings. Updated by using drupalSettings
Attached is a more universal patch that update headers with its original format and token replacement. Ideally footer / no-result-behavior should have same update but I don't bother include these in my patch.
attach based on 8.x-1.0
wangshy → created an issue.