Implementation Rules
Reviewed Implementation Rule
9 record(s) in Drupal Knowledge 1.1.3. Every entry below carries the same trust class.
- Exported configuration depends on a module the same export does not enableA config object declares a module dependency, and that module is absent from the complete list of modules the same exported core.extension enables.
- The exported default theme is not enabled by the same exportsystem.theme names a default theme that is absent from the complete list of themes the same exported core.extension enables.
- No single exported configuration root could be selectedMore than one plausible exported configuration root was found, so no exported configuration was enumerated and configuration rules cannot be evaluated.
- CSS or JavaScript aggregation is disabled in exported configurationThe exported system.performance configuration disables CSS or JavaScript aggregation. Drafted pending an authoritative source that states the expected production value.
- Browser and proxy cache maximum age is zeroThe exported system.performance configuration sets the browser and proxy cache maximum age to 0, so Drupal tells browsers and proxies not to store the page.
- Views cache strategy could not be read from exported configurationExported views configuration exists but the repository's safe YAML reader cannot parse it, so no view's cache strategy was observed either way.
- Trusted host patterns are not declared in the observed settings fileDrupal's trusted host mechanism is enabled by declaring $settings['trusted_host_patterns']. No such declaration was observed in the settings files this analysis read.
- update.php access control is disabled$settings['update_free_access'] is declared TRUE, which removes the access check in front of the update.php script.
- Verbose error display is exported without observable environment contextThe exported system.logging configuration displays all errors including backtraces. Whether that is wrong depends on the environment, which this analysis cannot observe.