Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.My use case is that I want to create a sub profile of the BuildKit profile (which is based on Profiler).
Everything works fine except that I need to add all module files to my own child profile (or to it's own .make file). If I don't do so the installer will detect dependencies inherited from BuildKit as missing and tell me to include those dependencies in the profile folder. It would be nice to always include modules from the base profile somehow.
I know that this is a limitation of the Drupal installer, more than a Profiler issue. But I thought that I'll submit an issue here to see if someone can come up with some kind of a workaround.
My temporary solution is to always include symlinks in my child profiles that links back to the base profile's modules, themes and libraries. Even though the child profile always knows where the base profile exists (../base_profile/) this doesn't feel like a sustainable solution.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | drupal-allow_modules_and_themes_in_profiler_base_profiles-970980-5-D7.patch | 728 bytes | arnested |
Comments
Comment #1
q0rban commentedYeah, I'm not sure here. If you can get the modules into sites/all/modules instead, you can circumvent this problem. Maybe modify the drush_make file to specify the directory you'd like the modules to be downloaded to?
If that doesn't suffice for you, I'd open an issue on drush_make or Drupal core, as this really is outside of the control of Profiler.
Comment #2
thedavidmeister commentedputting stuff in sites/all/modules doesn't sound like the best option. Means that you can't build the base profile with the same stub make file that you build the sub profile with.
at first I didn't like the symlink suggestion, but if the child profile actually has a variable that contains the path to the base profile this could work as part of the install script.
can we access profiler's variables like that in the install script?
Comment #3
thedavidmeister commentedUnfortunately there's a relatively heated discussion over here #913148: Please bring back install_path that basically screw the whole idea of getting modules from the base profile into sites/all from within the base profile's make file.
Comment #4
arnested commentedAs a workaround I have attached a patch that hacks core (keep your kittens inside) with support for profilers base profile.
The hack is for Drupal 7.
Comment #5
arnested commentedUpdated version of core hack - the previous one messed with a variable that was none of its business...