To prevent memory problems I updated my installation profile from uuid_features alpha4 to the latest dev, and used the option 'Package files with generated module.'.

During installation I got this:

Unknown error occurred attempting to import file: [error]
Undefined property: stdClass::$uri in _uuid_features_file_field_import_file() (line 646 .../uuid_features/uuid_features.module).

but when reverting after installation it worked fine and files were imported.

Any idea on why it broke during installation? should the module do a module_load_inlcude of some dependency?

related issue: https://www.drupal.org/node/2411869

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

JurriaanRoelofs’s picture

Issue summary: View changes
JurriaanRoelofs’s picture

it seems that the work in this module has caused a number of problems, there is also a strange regression that causes my installation profile to corrupt the database when uuid_features is installed together with file_entity
If anyone is googling this error:
EntityMalformedException: Missing bundle property on entity of type bean. in entity_extract_ids() (line 7836 of ../includes/common.inc).
Then now you possibly know why your Drupal site is not exporting bean blocks anymore.

JurriaanRoelofs’s picture

I fixed a number of bugs in importing and exporting of files that are packaged with the module, which was especially buggy when file_entity module is also installed.
Using this patch it works without problems but the bean issue I mention in #2 still persists.

JurriaanRoelofs’s picture

Status: Active » Needs review
das-peter’s picture

Status: Needs review » Fixed

Patch looks good to me - just found one minor nitpick:

+++ b/uuid_features.module
@@ -643,12 +643,19 @@ function uuid_features_file_field_import(&$import, $entity_type, $module = NULL)
+  // The file is referenced but not defined because it's already
+  // contained in a file_entity include

Inline comments must end in full-stops, exclamation marks, or question marks.

Fixed that while committing and pushing this.
Shall we open a dedicated issue for #2?

Status: Fixed » Closed (fixed)

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