## Problem/Motivation Applying the recipe on an installed site (`drush recipe recipes/ogcb`) currently fails, and two of the patches in `patches.json` no longer apply against the versions the Composer constraints resolve to. Both need fixing before the recipe installs cleanly again. ### 1. Organization field configs use `null` Three field configs ship `null` for `required` and `translatable`: - `config/field.field.user.user.field_organization_name.yml` - `config/field.field.user.user.field_organization_city.yml` - `config/field.field.user.user.field_organization_country.yml` ```yaml required: null translatable: null ``` Core's `field_config_base` types both as `boolean` and marks the type `FullyValidatable`, which implies `NotNull`. `Drupal\Core\Recipe\RecipeConfigInstaller::installRecipeConfig()` validates every `FullyValidatable` config it creates and throws: ``` There were validation errors in field.field.user.user.field_organization_name: - required: This value should not be null. - translatable: This value should not be null. ``` Six violations in total, two per file. Checked all 80 `field.field.*` files in the recipe — these three are the only ones affected. This only bites when the recipe is applied to an already installed site. `RecipeConfigInstaller` skips validation while `InstallerKernel::installationAttempted()` is true, so applying the recipe during site install passes silently and leaves invalid config behind. That is likely why it went unnoticed. ### 2. `patches.json` is out of date `#3564079` (core) fails on the `navigation.schema.yml` hunk. Core 11.4 changed the `ValidKeys` constraint from the shorthand form to the nested `allowedKeys` form, so the context no longer matches. `#3590990` (entity_hierarchy) failed with 6 of 7 hunks rejected in `entity_hierarchy.module`. MR !72 was written against 5.0.0-alpha9; 5.0.0-rc1 moved the hooks to `src/Hook/EntityHierarchyHooks.php` using `#[Hook]` attributes. The Composer constraint `^5.0.0-alpha9` resolves to rc1, which is what triggers it. `group_features` has no entry at all, but needs one: it ships no config schema for the `group_features` field type, so importing `field.storage.group.field_features.yml` and `field.field.group.community.field_features.yml` fails with three "unknown key" violations on `target_type`, `handler` and `handler_settings`. ## Steps to reproduce 1. `composer install` on a fresh checkout — two patches fail to apply. 2. Install Drupal 11.4, then run `drush recipe recipes/ogcb`. 3. The recipe aborts with the validation errors above. ## Proposed resolution **Config.** Set both keys to `false` in the three files, which is what the UI writes and what every other `field.field.*` config in the recipe already does: ```yaml required: false translatable: false ``` **patches.json.** Three changes: ``` drupal/core, #3564079 - https://www.drupal.org/files/issues/2026-06-18/config-show-local-tasks.patch + https://www.drupal.org/files/issues/2026-09-04/core-3564079-show-local-tasks.patch ``` A pure context reroll of the patch in comment #34, added lines unchanged. ``` drupal/entity_hierarchy - "#3590989 - Fix recipe install TypeError in selection handler for entity_reference_hierarchy fields" + "#3590990 - SelectionPluginManager is unable to get plugin Id from deriver if instance not(yet) present" ``` The URL stays `https://git.drupalcode.org/project/entity_hierarchy/-/merge_requests/72.diff`. MR !72 has been updated: 5.x is merged in and the two `field_storage_config` hooks are ported to `EntityHierarchyHooks`, so it applies against rc1 again. The old description also referenced the wrong issue — `#3590989` is closed, `#3590990` is the open one the MR belongs to.