I'm not convinced this is a focal_point issue, but don't have time for further debugging atm.

If I perform a new site install and then enable modules in the following order: -- 1) uuid, 2) focal_point --, I get the following errors:

WD php: PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'uuid' in 'field list': INSERT INTO {file_managed} (uid, filename, uri, filemime, filesize, status, timestamp, uuid) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3,
:db_insert_placeholder_4, :db_insert_placeholder_5, :db_insert_placeholder_6, :db_insert_placeholder_7); Array
(
    [:db_insert_placeholder_0] => 1
    [:db_insert_placeholder_1] => test-drive.jpg
    [:db_insert_placeholder_2] => public://focal_point/test-drive.jpg
    [:db_insert_placeholder_3] => image/jpeg
    [:db_insert_placeholder_4] => 497845
    [:db_insert_placeholder_5] => 1
    [:db_insert_placeholder_6] => 1461764005
    [:db_insert_placeholder_7] => 0667f74e-3e46-4e8f-acd0-a9d9d5723173
)
 in drupal_write_record() (line 7334 of /var/docroot/web/docroot/includes/common.inc).
Cannot modify header information - headers already sent by (output started at /home/vagrant/.drush/includes/output.inc:38) bootstrap.inc:1249

Steps to reproduce:

drush si minimal --account-name=admin --account-pass=pass -y; drush en uuid -y; drush en focal_point -y
= Errors

drush si minimal --account-name=admin --account-pass=pass -y; drush en uuid -y; drush en file -y; drush en focal_point -y
= No Errors

drush si minimal --account-name=admin --account-pass=pass -y; drush en focal_point -y; drush en uuid -y
= No Errors

Comments

Chris Gillis created an issue. See original summary.

bleen’s picture

Something is strange here ... focal point has a dependency on the "image" module which in turn depends on the file module. So by definition, enabling the focal point module will first enable the file module.

/me scratches brain

Chris Gillis’s picture

@bleen: Have you tried those drush commands? Can you replicate the same issue? It's not just my environment right? I wonder if this is a deeper issue with Drupal not handling grandchild dependencies very well...

bleen’s picture

I wonder if Drupal tries to enable dependent modules in parallel instead of serially. This would actually explain some weird (unrelated) behaviors I've seen with Features in the past.

... havent had a chance to try your drush commands and confirm error

Chris Gillis’s picture