Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Running our CI over a multilingual drupal site we saw this issue with Devel Node access.
Drupal\KernelTests\Core\Config\DefaultConfigTest::testDefaultConfig
Schema key devel_node_access.settings:langcode failed with: missing schema
Adding the schema key fixed this, and a patch is attached for this
Comment | File | Size | Author |
---|---|---|---|
#7 | devel_node_access_schema_langcode.patch | 543 bytes | Tom.W |
Comments
Comment #2
willzyx CreditAttribution: willzyx commented@Tom.W thanks for reporting.
DNA for D8 has temporarily moved to its own project until it's ready. Moving the issue to DNA issue queue
Comment #3
Tom.W CreditAttribution: Tom.W commentedno problem. Does the above patch work for you? Seemed to solve the issue on my copy
Comment #4
miro_dietikerPatch doesn't apply here, let's get testbot triggered still.
Comment #5
miro_dietikerah, no testbot here.. Patch still needs reroll.
Comment #6
Tom.W CreditAttribution: Tom.W at PwC's Experience Center commentedRerolled patch for new module, should apply cleanly now
Comment #7
Tom.W CreditAttribution: Tom.W at PwC's Experience Center commentedsorry, noticed issue with indentation after i uploaded, cleaned it up in this one. It applies for me (using patching via composer) so let me know if you have any issues
Comment #8
salvisI'm confused—where is this used? DNA has no such setting.
In fact, DNA has no tests, which is why we can't run testbot on it.
Was this issue somehow related to DNA being part of Devel?
Comment #9
Tom.W CreditAttribution: Tom.W at PwC's Experience Center commentedSchema testing is a core test that runs over every module on a site and checks for the schema existing and being correct, so although its not part of the module itself your module does get tested.
See \Drupal\KernelTests\Core\Config\DefaultConfigTest
Comment #10
Tom.W CreditAttribution: Tom.W at PwC's Experience Center commentedComment #11
salvisYes, but there's no langcode setting in DNA.
Comment #12
Tom.W CreditAttribution: Tom.W at PwC's Experience Center commentedand that is why it fails..... The schema test always requires you to have a langcode of some kind defined. Maybe that makes this an error in that test ;) but the easy fix is to add the key as per the patch above
Comment #13
salvisOk, I'll add it, thanks!
Would you have a pointer to where this is documented? Do I need to set a certain value, given that DNA doesn't care about language?
P.S. Right now there's still an issue with the testbot: #2853814: Composer require failure: Devel vs. Devel Node Access