This issue exist on several sites after Upgrading to 10. This issue is fatal as it is not repeatable and really rare, but it crashes the sites output until someone does a cache refresh.
As Drupal does not even address this issue as relevant we have to patch the core file to run a cache refresh when the error is created. Nasty as it is.
We also got screenshots of the client showing that the site comes totally blank without any loaded assets (js and css) from now and then since this issue exists.
This happens daily dozens of times sind the D10 Upgrade (latest 10.2)
Why is this bug marked as fixed? For that would have been a stopper for the D10 Upgrade.
mogio_hh → created an issue.
What is fixing the issue?
The patch? Upgrading to 10 is no Option in this moment.
Is there a downgrade solution thats works for the module?
Drupal 10 Upgrade is planned in Nov. Until then Paragraphs must be usable somehow
mogio_hh → created an issue.
mogio_hh → created an issue.
Me too.
#25 should make it into the main version.
Client wanted us to remove the whole focal point module as he had to reset the focal point on "each" node change.
Thanks god we found this issue...
It also works within initially closed paragraphs + field groups.
Is there any Drupal website these days that is not using Paragraphs and field groups?
Again :)
#25 should make it into the main version!
Note: #35 does not work with the 6.0.1 nor the latest dev.
Is there a changed that this will be fixed?
So this means Drupal Commerce is not usable for headless projects like NextDrupal for example due to compatibility issues with JSON:API Extras? - Is there any headless Drupal project, that is not using "JSON:API Extras"?