From what I can tell, you cannot install this module using an installation profile. The reason for this is found in the following code block (lines 30-36 of soundmanager2.install):
if ($phase == 'install') {
$requirements['soundmanager2']['title'] = $t('SoundManager2');
$requirements['soundmanager2']['value'] = $t('SoundManager2: remember!');
$requirements['soundmanager2']['description'] = $t('You must install <a href="@soundmanager2">SoundManager2</a> to %sm2dir, or <a href="@sm2settings">configure its installation path</a>.', array('@soundmanger2' => 'http://www.schillmania.com/projects/soundmanager2/doc/download/', '%sm2dir' => $sm2_path, '@sm2settings' => url('admin/settings/soundmanager2')));
$requirements['soundmanager2']['severity'] = REQUIREMENT_INFO;
return $requirements;
}
According to the instructions found here, you cannot depend on the full drupal API when you are in the "install" phase of hook_requirements:
Note that the installation of a module can happen during installation of Drupal itself (by install.php) with an installation profile or later by hand. As a consequence, install-time requirements must be checked without access to the full Drupal API, because it is not available during install.php.
The block of code listed above uses the url function, which I don't think is actually available if it's being installed from an installation profile. Furthermore, it seems that the $sm2_path variable is out of scope when this module is installed with an installation profile, so I get an "undefined variable" and WSOD when I try to install.
The attached patch fixes both of these issues.
Thanks again for your work!
Comment | File | Size | Author |
---|---|---|---|
install_requirements.patch | 1.09 KB | ldweeks | |
Comments
Comment #1
davebv CreditAttribution: davebv commentedThanks for reporting the bug, your patch has been applied in the latest commit. A new release will be ready.