Problem/Motivation

Since the switch to using Apps in #1459162: Provide features via Apps, installation with Drush fails. Since Aegir installs a site using Drush, Aegir also fails.

Proposed resolution

Need to apply a version of the patch at #1561652: Allow Apps to Be Installed with Drush During Site Install.

Comments

nedjo’s picture

I posted a new patch at #1561652: Allow Apps to Be Installed with Drush During Site Install but don't have time ATM to test.

Robin Millette’s picture

nedjo’s picture

Thx for testing!

I've added the latest patch from #1561652.

nedjo’s picture

Status: Active » Fixed

Seems to be fixed. Pls reopen if not fixed in dev or in the next release (rc3).

nedjo’s picture

Needed to refresh and fix an error in the patch from #1561652.

jayelless’s picture

Status: Fixed » Needs work

I have experienced a few problems with Open Outreach 7.x-1.4 not installing correctly in my aegir environment.

The most noticable is that the provided default theme of Granada fails to be selected. The install log contains the following lines:

...
WD system: debut_social module enabled.
WD system: wysiwyg module installed.
WD system: wysiwyg module enabled.
WD system: debut_wysiwyg module installed.
WD system: debut_wysiwyg module enabled.
Undefined index: theme openoutreach.install.inc:472
WD features: Rebuilding debut_article / field.
WD features: Rebuild completed for debut_article / field.
WD features: Rebuilding debut_article / user_permission.
WD features: Rebuild completed for debut_article / user_permission.
...

and looking into the file openoutreach.install.inc at line 472 showed

function openoutreach_theme_form_submit($form, &$form_state) {
  // Enable and set the theme of choice.
  $theme = $form_state['input']['theme'];
  theme_enable(array($theme));
  variable_set('theme_default', $theme);

When I changed line 472 to read

  $theme = $form_state['values']['theme'];

then the default theme was correctly set to Granada.

Another error that shows up in the aegir install log is:

...
WD features: Rebuild completed for debut_wysiwyg / filter.
WD features: Rebuilding debut_wysiwyg / user_permission.
WD features: Rebuild completed for debut_wysiwyg / user_permission.
WD cron: EntityMalformedException: Missing bundle property on entity of type file. in entity_extract_ids() (line 7562 of /var/aegir/platforms/openoutreach-7.15-1.0-rc4/includes/common.inc).
WD cron: Cron run completed.
Changed permissions of sites/a103.myweb.lan to 755
Changed permissions of sites/a103.myweb.lan/themes to 2775
...

I don't know yet what the impact on functionality of the exception reported above is - Possibly nothing.

There are aslo a couple of other "undefined index" errors that I have spotted:

...
WD system: rdf module enabled.
WD system: search module installed.
WD system: search module enabled.
Undefined index: module user.module:1860
WD system: openoutreach module installed.
WD system: openoutreach module enabled.
WD actions: Action 'Publish comment' added.
WD actions: Action 'Unpublish comment' added.
WD actions: Action 'Save comment' added.
...

and

...
WD features: Rebuilding openoutreach_core / user_permission.
WD features: Rebuild completed for openoutreach_core / user_permission.
WD user: Session opened for admin.
Undefined index: op openoutreach.install.inc:179
WD system: views module installed.
WD system: views module enabled.
...

which probably need to be followed up. I am not yet aware of whether either of these has an effect on site functionality.

jayelless’s picture

Woops. I should have said that I am using version 7.x-1.0-rc4. I don't want to get too far ahead of myself :)

nedjo’s picture

Thanks for the detailed notes. Yes, these problems look to reflect values that are passed only in an interactive install. I'll have a look at fixing this up.

nedjo’s picture

Status: Needs work » Fixed

Applied a version of the fix suggested in #6. Didn't spend the time to track down the user module related warning, but at least we should get a couple fewer warnings and the theme enabling correctly. Thanks jlscott!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.