Problem/Motivation
varbase.info.yml installs the front-end and admin themes for every Varbase site:
themes: - gin - vartheme_bs5
Varbase 11 installs a site template, and there will be several of them, each owning its own themes. Every site template already installs and sets both: varbase_starter sets vartheme_bs5, educare sets vartheme_bs5_educare, horizonaid sets its own, and gin is installed by varbase_admin_base and set as the admin theme by drupal_cms_admin_ui. Both of those are applied by every site template, so the profile does not need to install either theme.
Steps to reproduce
- Install Varbase 11 and choose the Educare site template.
drush pm:list --type=theme --status=enabledvartheme_bs5is installed although the default theme isvartheme_bs5_educareand nothing uses it.
Proposed resolution
Make the profile's themes an explicit empty list:
# Explicitly provide an empty list of themes: this prevents the installer from # injecting Stark into it, and lets each site template install and set its own # front-end and admin themes. # @see install_profile_info() themes: []
The key is kept rather than removed, because install_profile_info() injects Stark when a profile declares no themes. This is the same approach drupal_cms_installer takes.
The installer is unaffected: distribution.install.theme is varbase_installer_theme, whose base theme is claro. The themes also stay downloadable, since the profile requires drupal/varbase_starter.
Verified from a dropped database, with both site templates: the correct default theme, admin: gin with Gin assets rendering on /admin/content, no Stark installed, front page 200.
Remaining tasks
- ✅ 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
User interface changes
- None visible. Each site template continues to set its own front-end and admin themes; only the profile's redundant installation of them is dropped.
API changes
- N/A
Data model changes
- N/A
Release notes snippet
- The Varbase profile no longer installs the front-end or admin theme. Each site template installs and sets its own.
Issue fork varbase-3614696
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
rajab natshahComment #4
rajab natshah