...and my use case was when rendering a render array for a content in an email context, so I replaced \Drupal::service('renderer')->render($myRenderArray) with \Drupal::service('renderer')->renderInIsolation($myRenderArray) and did the trick... It seems that renderInIsolation is used exactly in these kind of contexts: https://api.drupal.org/api/drupal/core%21lib%21Drupal%21Core%21Render%21...
I'm stucked with exactly the same bug, causing specifically Scheduler cron job to fail.
I also confirm that #13 works in D10.3 + layout_builder_st alpha3 + layout_builder_modal 1.2
#18 worked perfectly for me using Drupal 10.3.1. Before the patch, some views didn't apply the DISTINCT in the query despite of being enabled in the views config. After applying it, all of them worked.
I also confirm that #26 works with D10.3.1 and LB Symmetric alpha3
Can confirm patch #43 worked for me too with Drupal 10.3.1 and Paragraphs 1.18.
Thanks for reporting! I'm sorry, but Drupal origins is not useful anymore, so we won't fix it.
Drupal Origins was a great kickstarter back in D7, but back then we couldn't move it to the D8+ ecosystem and now it doesn't make sense anymore. I'll close the issue.
Subscribe to this issue, I think that Symettric translations should be covered by core, leaving the Asymettric translations in the already stable contrib module.
+1
This one did the trick for me too, thank you!
joe_carvajal → created an issue.
I confirm that the bug is still present in Drupal 10.1.6.
The patch in #32 works and applies to D10.1.* perfectly.
#17 seems to be working fine in D10. Thank you!
joe_carvajal → created an issue.
Patch #2 works perfectly for me with these versions:
- PHP 8.1.18
- Drupal 9.5.9
- Group 8.x-1.5
But reading the docs I decided to move to Group 2.1, as recommended. By the way, the GroupPermissionHandler.php file has the patch applied there.
I subscribe to this issue and also think it's critical due to 9.5.8 is a security update: https://www.drupal.org/project/drupal/releases/9.5.8 →
Subscribe.
Thank you @mrweiner for #8 and #16 for the platform.sh config. They made my day.
Hey. After having a look at this one, this is not a Profile module issue, it's a core issue itself.
It's being discussed and worked here:
https://www.drupal.org/project/drupal/issues/3300404
📌
Unserialize(): Passing null to parameter #1 ($data) of type string is deprecated in Drupal\Core\Entity\Sql\SqlContentEntityStorage
Needs work
There are event patches for that, but they've not been approved yet. I think that #28 is going to do the trick for me at least, despite of I'm aware that it may be a temporary solution.
Subscribe, having the same Warning.
Just to push this up, the patch at #56 looks nice but it does not apply with new 4.0.0 version.
I confirm that the issues persist at 4.0.0.
I had this issue, updated from 3.0.2 to 3.0.9 and got it solved.
So probably the fix is somewhere between these two versions.