fix: #3610876 Install Vartheme BS5 and correct the invalid component UUIDs

What

Two problems, both required for Varbase News Base to install cleanly from a site template with its own theme:

1. Missing theme dependency. The recipe's Canvas content templates (hero card, text card large/medium/small) render through Vartheme BS5 components. Config actions are validated on apply, so if the theme is not installed the recipe aborts. Drupal Canvas only generates a theme's Component config entities on RecipeAppliedEvent — after a recipe finishes — so installing the theme inside the same recipe would not help; it must be installed by a recipe that finishes earlier. Fix: vartheme_bs5 added to install, same as Varbase Events Base.

2. Invalid UUIDs on 4 Canvas content templates. canvas.content_template.node.news.hero_card, .text_card_large, .text_card_medium and .text_card_small each carried a component-tree UUID with an invalid variant nibble (e.g. c1e4f5a6-c7d8-4290-1234-789012345689 — 1234 is not 8/9/a/b), inherited from the Varbase Blog Base templates these were cloned from. A recipe's config files are imported without validation, so the invalid UUID goes in unnoticed. It only surfaces once something validates the entity — e.g. a site template repointing the tree onto its own theme via the repointComponentTreeToTheme config action — which then aborts the install with:

component_tree.<uuid>.uuid: This is not a valid UUID.

Fix: the four UUIDs are regenerated as valid v4/v5 UUIDs.

Varbase Blog Base carries the same invalid UUIDs (same clone origin) and needs the identical fix as a follow-up.

Issue

Closes #3610876: https://www.drupal.org/project/varbase_news_base/issues/3610876

AI disclosure

AI-Generated: Yes (Added vartheme_bs5 to the recipe's install list, regenerated the 4 invalid component-tree UUIDs, and wrote this MR description; reviewed by Rajab Natshah.)

Checkpoints

  • 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
Edited by Rajab Natshah

Merge request reports

Loading
Loading