- 🇳🇱Netherlands tinto Amsterdam
I've tried (again) to isolate/reproduce the problem on a clean Drupal (9.5.11) install with only the Antibot and Cookiebot modules enabled, but I was unsuccessful.
The issue does still persist in several different client sites, but I cannot figure out what combination of modules and settings is causing this. In my case(s) it seems Cookiebot is blocking the Antibot script that should replace
action="/antibot"
withaction="/user/login"
in the form element, until the user agrees to all cookies and reloads the page. I'm seeing the problem in all forms that have Antibot protection applied.Question to others who see this issue: does this problem still persist when you disable Automatically block all cookies in
/admin/config/cookiebot
? - 🇦🇺Australia gordon Melbourne
This problem seems to be related to #2738051 🐛 \Drupal\views\Plugin\views\query\Sql::getCacheTags and getCacheMaxAge don't take into account that some entities can be NULL Needs work , but in my case the other didn't fix my issue but caused another issue, and this one fixed it. They both seem to be a very similar issue and solved in slightly different methods.
in_array(): Argument #2 ($haystack) must be of type array, null given in in_array()
core/modules/ckeditor5/ckeditor5.module(635): in_array('codeBlock', NULL, true)in_array(): Argument #2 ($haystack) must be of type array, null given in in_array()
core/modules/ckeditor5/ckeditor5.module(635): in_array('codeBlock', NULL, true)- 🇨🇭Switzerland sir_squall
I still got this error, when we are using the :
$node = \Drupal::routeMatch()->getParameter('node');in this hook:
_preprocess_html(&$variables) {we have this preg_quote error
- 🇫🇷France fgm Paris, France
@2dareis2do 's answer on Slack :
My patch is just a collection of other peoples commits so I am not sure I am the best qualified person to review this. This patch has been working for me though. In the meantime I have decided to restrict stats view to registered users as as well.
- 🇺🇸United States RobbyMo
Similar issue for me when going to the /admin/reports/config-inspector page after upgrading to the latest version:
Symfony\Component\Validator\Exception\UnexpectedTypeException: Expected argument of type "array", "null" given in Drupal\Core\Validation\Plugin\Validation\Constraint\ValidKeysConstraintValidator->validate() (line 23 of /var/www/html/web/core/lib/Drupal/Core/Validation/Plugin/Validation/Constraint/ValidKeysConstraintValidator.php).
After downgrading back to the previous version that I was using (2.1.0) the error goes away.
- 🇪🇸Spain rodrigoaguilera Barcelona
Deleting the
core.base_field_override.*.*.moderation_state.yml
worked for me. They were created by saving the content translation form and just like in comment #12 they did not change anything from the defaults so there was no need for an override.
After exporting the config, trying to install the site from that config leads to the error from the IS.
- 🇹🇭Thailand manarak
@pameeela
if I knew if the bugs were related or duplicates, it would mean I knew the exact nature of the bug, but I don't. - 🇦🇺Australia pameeela
@DrupalDope are the issues related or duplicates? If they are duplicates, it is more likely to be resolved if all but one are closed, so that all work is being done toward the same resolution.
- 🇳🇱Netherlands Lendude Amsterdam
Since it seems to break on \Drupal\views\Plugin\views\query\Sql::create() maybe a patch that was updated (but might be broken) during the upgrade?
Does the problem go away if you remove all patches from the project?
- 🇫🇷France Nicolas Bouteille
UPDATE : in the end the number of errors that appear in the logs seems to clearly decrease, so this clearly seems to be due to Drupal 9 pages being kept open on an old tab that requests CSS and JS files the old way not compatible with D10. So not much to do here, the errors should fade away progressively...