Hi @smitghelani,
I had the same problem with an older site with the Lightning distro on and I fixed it by adding this in my composer file:
"patches-ignore": {
"drupal/lightning_core": {
"drupal/core": {
"2869592 - Disabled update module shouldn't produce a status report warning": "
https://www.drupal.org/files/issues/2869592-remove-update-warning-7.patch →
"
}
}
}
Hope that helps you!
interactivex → created an issue.
I can confirm that the solution in comment #4 🐛 Warning: Trying to access array offset on value of type null in gutenberg_form_node_form_alter() (line 578 of gutenberg.module). Active is working
I got this to work again by adding the following patch to the Gin theme https://www.drupal.org/project/gin/issues/3460150 🐛 Save button missing when using the Gutenberg/Mercury editor module Fixed
The patch didn't work for version 4.0.1 so I created a patch for that version. I can confirm now the images do work again.
interactivex → created an issue.
Created a patch to fix the error.
We have the same problem with using the pager in the media library pop-up. It seems to have something to do with an error already reported here: https://www.drupal.org/project/yoast_seo/issues/3416502 🐛 Error with libraries Active
Furthermore, I have developed a patch on top of the #68 patch that incorporates the logic to verify whether the facets block is located on a different page than the search results page. In our scenario, the facets blocks are positioned on the homepage, while the search results reside on their own dedicated page.
I hope this proves beneficial to someone.
I've added the Facets Summary block and I see the submit button. Only when I submit it's not going to the results page. I have the facets in a separate block on the homepage and when submitting it should go to the /search page, but now it stays on the homepage. Any idea on how to solve that?
Sorry ignore the last patch. This one is the right patch. I had to change $editor->id() to $editor->getEditor().
Here is the patch I created to fix this.
interactivex → created an issue.
Thanks for the great job @JoaoCoelho13. Your patch is only missing the missing dist JS. I've added it to a new patch.
Unfortunately we also see this happening on one of our client's (high traffic) sites. For now we've uninstalled it and see if there will be a better solution to solve this. Randomly going down is not an option for this client.
Created the patch for this issue
interactivex → created an issue.