Install warns that the search-block_1 block plugin was not found, because the header region imports before the display is created

Problem/Motivation

Installing the Varbase Starter site template logs a warning on every install:

• [warning] The "views_exposed_filter_block:search-block_1" block plugin was not found

The warning is logged three times per install. The install still completes successfully and the header search renders correctly afterwards, so this is noise rather than a failure. It is an ordering problem inside the recipe.

The header region config in config/canvas.page_region.vartheme_bs5.header.yml places the exposed search form through the component block.views_exposed_filter_block.search-block_1. That block plugin is only provided once the block_1 display exists on views.view.search, and that display is created by a config action in recipe.yml.

Recipes import everything under config/ before running config.actions, so at the moment the header region is imported the display does not exist yet and the block plugin cannot be resolved. The plugin definition appears as soon as the action runs, which is why the warning is harmless and why nothing is broken after the install finishes.

Steps to reproduce

1. Install the site template: drush site:install varbase installer_site_template_form.add_ons=varbase_starter.
2. Read the install output. The warning above is logged, and the install then reports Installation complete.
3. After the install, confirm everything resolved: the block_1 display exists on views.view.search, the views_exposed_filter_block:search-block_1 plugin is defined, the header search box renders and no region reports a broken or missing block.

Proposed resolution

Make the block_1 display exist before the header region config is imported, so the block plugin is defined at import time and the warning stops. Options worth weighing:

• Ship the block_1 display as part of a config file the recipe imports rather than creating it through a config action.
• Split the header region config into a later step, so it is applied after the action that creates the display.
• Keep the current order and suppress or document the warning, if neither of the above is worth the added complexity.

No behaviour change is expected either way: the install already completes cleanly and the header search already works.

Remaining tasks

• ✅ File an issue about this project
• ❌ Addition/Change/Update/Fix to this project
• ❌ Testing to ensure no regression
• ➖ Automated unit/functional testing coverage
• ➖ Developer Documentation support on feature change/addition
• ➖ User Guide Documentation support on feature change/addition
• ➖ UX/UI designer responsibilities
• ➖ Accessibility and Readability
• ❌ Reviewed by a human
• ❌ Code review by maintainers
• ❌ Full testing and approval
• ❌ Credit contributors
• ❌ Review with the product owner
• ❌ Update Release Notes
• ❌ Release

User interface changes

• None. The warning is install output only.

API changes

• N/A

Data model changes

• N/A

Release notes snippet

• N/A