does not work.
Added a special case into
drupal_get_filename to make it work. It's a special case anyways as profiles can't live in sites/X/profiles as modules / themes / theme engines can. Also fixed a test that was using profiles as something not stored in the database to test
drupal_get_filename. Instead we abuse
drupal_get_filename capability to find any extension in a plural-named directory and added a dummy
test.script into the existing
scripts directory. We could've created a tests directory and put a single test in it but that would be confusing as it's not a simpletest. So another solution would be to create a
testfiles directory and put a single
test.testfile in it.
User interface changes
Original report by Steven Jones
Suppose one has an install profile called: 'stevens_profile' then one might want to do this:
$path = drupal_get_path('profile', 'stevens_profile');
As per the documentation for drupal_get_path. But that doesn't work. Now that profiles are recorded as modules in the system table, you need to do the following:
$path = drupal_get_path('module', 'stevens_profile');
Either the documentation needs to be changed or
drupal_get_filename needs to silently convert the 'profile' to a 'module' when doing the DB query.
|#68||drupal-1006714-68.patch||2.42 KB||Steven Jones|
|PASSED: [[SimpleTest]]: [MySQL] 36,952 pass(es).|
|PASSED: [[SimpleTest]]: [MySQL] 33,810 pass(es).|
|PASSED: [[SimpleTest]]: [MySQL] 33,820 pass(es).|
|PASSED: [[SimpleTest]]: [MySQL] 33,803 pass(es).|
|#46||drupal-1006714-46.patch||5.53 KB||Steven Jones|
|PASSED: [[SimpleTest]]: [MySQL] 33,802 pass(es).|