I recently came across this change record for D8: https://www.drupal.org/node/2952947
What this has done in short is that it has allowed installation profiles to specify install
dependencies in addition to the preexisting dependencies
. D8 uses .yml files, but here's how that could look in .info files:
name = Standard
description = Install with commonly used features pre-configured.
version = BACKDROP_VERSION
backdrop = 1.x
install[] = admin_bar
install[] = ckeditor
install[] = comment
install[] = dblog
install[] = views_ui
install[] = update
dependencies[] = node
dependencies[] = block
dependencies[] = color
dependencies[] = config
dependencies[] = contextual
...
The dependencies
array would be treated as a set of "hard" dependencies, meaning that they cannot be uninstalled, because the profile depends on them. If the profile simply wants to specify a list of modules to install, but upon which it does not actually depend, it can use the install
array.
To maintain backwards compatibility, profiles which only define a dependencies
array, but not an install
array, would have their list of dependencies treated like an install
list. This backwards compatibility layer could be removed in Backdrop 2.0, which should allow enough time for profile authors to separate their install
list from their actual dependencies.
Recent comments
I think given the warning on the source site: At this time, if your new project can afford to require PHP 5.5+, which it should, please use PHP's native password_hash() /...
July 31, 2025
I did a very quick test and if the Display format of the webform submission value is HTML then it appears but if plain text then it doesn't, so something is included regardless of if empty when...
"Hide rewriting if empty" has no effect
Just to clarify it appears that the item: Fix Search for "On the Web" module, is about the search on backdropcms.org at https://backdropcms.org/modules
July 31, 2025