EntityMalformedException with file_entity (media project) enabled [#1887106]

When the File Entity module (required by the Media project) is enabled, the following exception is raised after you create an import:

EntityMalformedException: Missing bundle property on entity of type file. in entity_extract_ids() (line 7647 of /var/www/drupal-7.x-dev/includes/common.inc).

Steps to reproduce:

Install standard Drupal 7.x-dev
Download and install media + user_import
Enable file_entity + user_import
Go to People > Import > New Import and create a first import
Go to People > List Imports

Quick and dirty workaround : define the file "type" in function _user_import_file_deletion of user_import.admin.inc by adding at line 672:
$file->type = 'user_import';

But a better integration with File Entity (using entity_get_info('file') ?) should be implemented.

Comment	File	Size	Author
#1	user_import-entitymalformexception_issue-1887106.patch	682 bytes	GaxZE

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

GaxZE CreditAttribution: GaxZE commented 22 February 2013 at 11:25

Version:	7.x-1.0-beta4	» 7.x-1.0-beta5
Status:	Active	» Needs review

File	Size
user_import-entitymalformexception_issue-1887106.patch	682 bytes

Thought i'd pop this fix into a patch - for me this was done on 7.x-1.0-beta5.

Excuse my patch name - trying to follow the naming conventions from: http://drupal.org/patch/submit

Comment #2

ace11 CreditAttribution: ace11 commented 2 April 2013 at 18:31

Works like a charm. Thanks!

Comment #3

FAAREIA CreditAttribution: FAAREIA commented 30 May 2013 at 15:23

Tested, works fine.
Using 7.x-1.0-beta6

Thanks

Comment #4

gisle

he/him

Norwegian Bokmål

Norway

CreditAttribution: gisle commented 6 July 2019 at 11:38

Version:	7.x-1.0-beta5	» 7.x-3.x-dev
Issue summary:	View changes
Status:	Needs review	» Postponed (maintainer needs more info)

I am unable to reproduce this bug with the lastest snapshot of User Import 7.x-3.x-dev in combination with Media 7.x-2.21 and File Entity 7.x-2.25, following the five steps outlined in the issue summary.

Can anybody confirm that this bug is still in the latest version of User Import 7.x-3.x-dev? And if "yes", please update the steps required to reproduce.

The patch in comment #1 does not apply (the code it patches has been moved from user_import.admin.inc to user_import.module). However, as noted in the issue summary, this should be resolved by better integration with File Entity.