0

我一直在尝试创建 Drupal 7 安装配置文件，但似乎某些模块对验证的名称install_verify_requirements()和实际模块安装目录（主要影响 unix/linux 安装）使用不同的大小写，这是一个示例：

# myprofile.info

name = myprofile
description = Some name for my profile
core 7.x

; Core
dependencies[] = block
dependencies[] = color
dependencies[] = comment
dependencies[] = contextual
dependencies[] = dashboard
dependencies[] = help
dependencies[] = image
dependencies[] = list
dependencies[] = menu
dependencies[] = number
dependencies[] = options
dependencies[] = path
dependencies[] = taxonomy
dependencies[] = dblog
dependencies[] = search
dependencies[] = shortcut
dependencies[] = toolbar
dependencies[] = overlay
dependencies[] = field_ui
dependencies[] = file
dependencies[] = rdf

; Contrib
dependencies[] = ctools
dependencies[] = features
dependencies[] = pathauto
dependencies[] = views
dependencies[] = entitycache
dependencies[] = storage_api

和

# myprofile.make
core = 7.x
api = 2
projects[drupal][type] = core

; Contrib Modules
projects[] = ctools
projects[] = features
projects[] = pathauto
projects[] = views
projects[] = entitycache
projects[] = storage_api

当你运行时：

drush make profiles/myprofile/myprofile.info

所有项目都毫无问题地下载到配置文件/myprofile/modules 中，但只要您尝试

drush site-install

您会收到错误报告，指出未找到 Storage_api 模块。您注释掉 storage_api 并且一切都按预期工作。

关于如何设置从 storage_api 到 Storage_api 的模块安装路径的任何线索，所以 install_verify_requirements() 函数实际上找到了应该找到的东西？或者以任何方式强制对此进行小写检查？

提前致谢 ！

4

1 回答 1

0

问题是实际上 storage_api 不包含任何称为 storage_api 的东西。相反，该myprofile.info文件应该包括

dependencies[] = storage
dependencies[] = storage_core_bridge
dependencies[] = storage_audit
dependencies[] = storage_audit_test

代替dependencies[] = storage_api

一般来说，这样做很聪明：

$ find ./modules/module -name "*.install"找到实际上可配置的dependencies[].

于 2013-05-09T04:21:48.110 回答