- Issue created by @dunx
- 🇳🇿New Zealand quietone
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
On Drupal CMS I see many instances of this message in my logs:
The following paths in /var/www/html aren't recognized as part of your Drupal site, so to be safe, Package Manager is excluding them from all stage operations. If these files are not needed for Composer to work properly in your site, no action is needed. Otherwise, you can disable this behavior by setting the package_manager.settings:include_unknown_files_in_project_root config setting to TRUE. README.md launch-drupal-cms.sh
Given only 1000 messages are retained by default, these are just noise. As a "marketeer" I can't do anything about them.
Base Drupal CMS installation on local.
I've done a few module updates through the UI... awesome work people.
As we know these two files will always exist for a Drupal CMS installation, can they be excluded from the test in some way to avoid this message appearing in the logs?
Active
11.1 🔥
package_manager.module
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .