Installing a site template through the browser installer (/core/install.php) intermittently fails during the recipe config batch with a PluginNotFoundException. It surfaces in two forms, seen on two different site templates:
PluginNotFoundException: The "redirect" entity type does not exist in Drupal\Core\Entity\EntityTypeManager->getDefinition()
PluginNotFoundException: Unable to determine class for field type 'image' found in the 'field.storage.user.user_picture' configuration
Both are the same mechanism: config that references a plugin whose providing module is not visible in that request. The redirect case reaches the entity type through trash's TrashEntityTypeManager decorator; the image case comes from drupal_cms_authentication applying core's user_picture recipe, which installs image and strictly imports that field storage.
Two things narrow it down:
drush site:install every time.drush cr: the module was installed all along.That points at container / module-registration staleness between batch requests in the RecipeKit install path, rather than at any individual recipe. Note the drush path masks it: builders typically run a cache rebuild straight after site:install, so the stale container never serves a request.
recipes/./core/install.php.Not yet determined, and deliberately not guessed at from the observations so far. The candidates are:
trash, redirect or RecipeKit.Filed as a report so the traces and the drush-versus-browser evidence are recorded. Reproducing it reliably is the first task.
Comments