fix: #3621845 Remove the 21 broken fallback Canvas component config files

Rajab Natshahrequested to merge
issue/varbase_starter-3621845:3621845-remove-broken-fallback-components into 1.0.x

Fixes #3621845.

Problem

The 21 config/canvas.component.sdc.vartheme_bs5.*.yml files were exported with active_version: fallback and an empty last_active_version. That sends Component::sourcePluginCollection() down the fallback branch, where Component.php:231 reads an undefined key — three PHP warnings per entity load, nine loads each per install: 567 warnings.

Canvas never generates these 21 (they are theme templates — form elements, regions, views wrappers), nothing recreates them, and nothing references them.

What changed

  • Removed the 21 broken config files.
  • Removed their 21 matching disable: [] actions in recipe.yml — a disable on config that is no longer imported fails the install, so both halves go together.

22 files changed, 315 deletions, no additions.

Verification

  • Clean drush site:install of the recipe: 567 warnings to 0, output 593 lines to 26. Reproduced on released 1.0.1 and again on 1.0.x-dev with Canvas 1.11.0.
  • Site afterwards has 104 Component config entities and none of the 21; front page, /features, /blog, /contact-us, /canvas and the Canvas editor all return 200; watchdog clean.
  • gitlab-ci-local: Composer validate PASS, YAML lint PASS (152 files, 0 invalid).

Pipeline

Re-run as pipeline 955301 after varbase-patches 11.0.43. 📐 YAML lint passes. Both pre-test install jobs still fail, for two reasons that are unrelated to this diff:

  • The Drupal CMS lane now resolves varbase-patches 11.0.43 and applies every patch cleanly, then fails later in the install with RequestStack.php line 115: There is currently no session available. — the Canvas 1.11.0 install defect, not this change.
  • The varbase lane still resolves varbase-patches 11.0.42, so it still hits the old No available patcher was able to apply patch ... canvas--2026-07-26--3560889--mr-1425.patch. That lane is removed by #3622098.

The verification above is from local installs, not from CI.

AI-Generated: Yes

Checkpoints:

  • File an issue
  • Addition/Change/Update/Fix
  • Testing to ensure no regression
  • Automated unit testing coverage
  • Automated functional testing coverage
  • UX/UI designer responsibilities
  • Readability
  • Accessibility
  • Performance
  • Security
  • Developer Documentation
  • User Guide Documentation
  • Reviewed by human
  • Code review by maintainers
  • Full testing and approval
  • Credit contributors
  • Review with the product owner
  • Release notes snippet
  • Release
Edited by Rajab Natshah

Merge request reports