Install
Works with Drupal: ^11.3Using Composer to manage Drupal site dependencies
Alternative installation files
Download tar.gz
27.12 KB
MD5: 565fede3bc988b7356eb2cdea0178b9a
SHA-1: 662297cf4ae8fcbc7bea1262c11cf87b515e3a4f
SHA-256: e5b45e2c1d084a6d7012a7fd1dac74ea1d80a21970f6a8439ca89b7d794a19df
Download zip
47.69 KB
MD5: f5083228d4bdda62c219fb035d0acd51
SHA-1: 385780515f6eb8b045b30141e00bce9ade9e0517
SHA-256: f9aefd2684c0ad5ac4147a497c95f1c504e9727bc4a14bf9fc50911923dd9236
Release notes
A few bug fixes, mainly in the installer and the site:export command-line tool. Configuration is now exported outside the web root by default, per best practices.
Contributors (7)
antiorario, brianperry, dorficus, mandclu, pameeela, phenaproxima, pritishkumar
Changelog
Issues: 8 issues resolved.
Changes since 2.1.0 (compare):
Bug
- fix: #3581778 Entity display form alter prevents enabling additional view modes
- feat: #3572886 The selected site template does not visually change when it receives focus by keyboard
- fix (drupal_cms_installer): #3582917 Increase the execution timeout for Composer operations in the installer
- chore: #3582753 Add canary tests that the config shipped by recipes is consistent when exported
- feat (drupal_cms_helper): #3584002 The site exporter should try to actually determine package names, rather than assuming they all start with `drupal/`
Feature
- feat (cms, cms_cpanel): #3580694 The project template should always place config outside the web root by default
Misc
- fix (drupal_cms_helper): SiteExportCommand should check that the base recipe directory is known before checking that it exists
- cleanup: Remove StorageCopyTrait from SiteArchiveCommand