Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Moved from #1773866: Use a makefile to drush make the distribution
I am actually trying to get this to work within an aegir environment and I can get the above makefile to build with drush make (not using --working-copy). However when I try and create an aegir platform using the makefile the verify is failing with the following error:
Drush command terminated abnormally due to an unrecoverable error. Error: Call to undefined function module_load_include() in /data/disk/o2o/static/julio-7.x-1.x-dev/profiles/julio/julio.profile, line 3
Output from failed command : Fatal error: Call to undefined function module_load_include() in /data/disk/o2o/static/julio-7.x-1.x-dev/profiles/julio/julio.profile on line 3
This is line 3 of julio.profile
!function_exists('feature_set_admin_form') ? module_load_include('inc', 'feature_set', 'feature_set.admin') : FALSE;
Any idea why aegir doesn't like this?
TIA,
JamieT
Comments
Comment #1
jgraham CreditAttribution: jgraham commentedI'm not too familiar with Aegir, it looks like whatever is running the verify process doesn't have a fully bootstrapped drupal environment and thus module_load_include() is not defined. I'm not sure if this is an aegir issue or if you perhaps just need to issue this command from within a fully bootstrapped environment.
Were you calling this verify command via drush? If so, were you also calling from within a drupal codebase?
Comment #2
jamiet CreditAttribution: jamiet commentedThanks for responding. The verify drush command is called by aegir when you run the verify task on the platform within the aegir front end. I ran the drush command manually with the --debug switch and have pasted the output below:
Not sure if the above helps shed any further light on this?
TIA,
JamieT
Comment #3
jgraham CreditAttribution: jgraham commentedI believe this is an issue with Aegir's provision-verify as Drupal.org's makefile verify works okay with julio's drupal-org.make makefile. I'm not sure where this issue should move to as there are no Drupal 7 aegir projects;
http://drupal.org/project/hostmaster
http://drupal.org/project/provision
I'm assuming provision is the right location for this, but I'm not sure. Feel free to bounce this wherever it needs to be. In the meantime I'm moving to strictly postponed and "support request" as I have no intention of fixing this without further details about what level of bootstrap Aegir's provision-verify runs at and why module_load_include() is not included in that bootstrap level. My best guess is this is due to the fact that the Aegir provisioning system is running outside of the julio codebase and cannot *and should not* assume to load any Drupal boostrap level details.
If I get more details on a possible workaround to this shortcoming in Aegir I'm open to patching/adjusting Julio's architecture. Alternatively if distributions should not be calling module_load_include() then we should update api.drupal.org and adjust julio as appropriate.
Comment #4
jamiet CreditAttribution: jamiet commentedThanks for your feedback - sorry in delay for some reason I didn't get notified?
I will raise this issue on the provision project and see if they can help get to the bottom of this.
edit: Just in case someone else wants to track this I raised issue #1807516: Incompatibilty between multiple distro's and Aegir Call to undefined function module_load_include() when calling platform verify on the provision issue queue.
Thanks,
JamieT
Comment #5
jgraham CreditAttribution: jgraham commentedJust a thought is you php version >= 5.3? Julio requires php 5.3+ as the base theme hexagon needs php 5.3.
Comment #6
jgraham CreditAttribution: jgraham commented