As part of the Event Platform initiative, I am working on a recipe to provide a robust starting point for a Drupal camp website. The content architecture of Drupal CMS overall is too opinionated to be suitable as a starting point, but I would like to use individual recipes as a way to align with best practices being established here.
In particular, I would like to use drupal_cms_admin_ui as a way to install the Gin admin theme and some other admin improvements. Unfortunately, applying the recipe on a fresh (standard) install of Drupal 11 yields unexpected results.
Here is an example of how the Extend page looks before applying the recipe:
And here is how it looks after:
It appears that somehow the recipe puts a large number of blocks intended for the front end into the header region of the Gin admin theme.
On a fresh, standard install of Drupal 11, apply the drupal_cms_admin_ui recipe, and then go to any administration page, such as the Extend page.
I'm not sure what is causing this behaviour. I did notice that if I manually install Gin before applying the recipe then the extra blocks are not visible. So it's possible it is somehow a by-product of using the recipe runner to install a theme.
Active
Track: Gin admin theme
Could you try on Drupal 11.2? I believe it could be fixed by this:
Thanks Jim. I can confirm that when applied on a dev version of Drupal 11.2 the extra blocks do not appear.
To follow up, there are patches that are RTBC for this waiting to be ported back to 11.1, 10.5, and 10.4. Hopefully we can get those landed soon.