When trying to edit (http://xxxxx.com/admin/commerce/orders/XXX/edit) an order, I'm getting the following error:

EntityMalformedException: Missing bundle property on entity of type commerce_customer_profile
(screenshot attached)

Did not find a solution, what might be wrong?

Thanks.

CommentFileSizeAuthor
#9 commerce-customer-missing-profile-type-1577596.patch1 KBberdir
#4 installed_modules.gif2.51 MBAbilnet
commerse-error-when-editing-an-order.png35.8 KBAbilnet

Comments

rszrama’s picture

rszrama commented
Version: 7.x-1.3 » 7.x-1.x-dev
Status: Active » Postponed (maintainer needs more info)

Hmm, nothing should cause this that I'm aware of. What other modules do you have on the site, and does that order possibly reference a non-existent customer profile?

rHOnDO’s picture

rHOnDO commented

Ryan;

I'm getting the same error when trying "Continue to next step" during checkout. I believe this step is supposed to automatically create a customer profile but it is not (there are no customer profiles in the db). I have also received the same error only referencing "commerce_product."

Be advised, this is an existing site which already had Commerce (just commerce and price) and addressfield modules installed, and it wouldn't let me follow the prescribed install sequence. I installed a test site on my local machine via Commerce Kickstart and it works without issue, but starting over from scratch is not an option on the existing site.

Here is the text of the commerce_product error, both errors reference the same line in common.inc:
EntityMalformedException: Missing bundle property on entity of type commerce_product.
in entity_extract_ids() (line 7501 of /var/aegir/platforms/blessed-drupal-7.x-2.0-alpha2/includes/common.inc).

rHO

rHOnDO’s picture

rHOnDO commented

@rszrama, @Abilnet;

I'm not 100% sure what worked, (I made numerous changes, manually changing tables, running commerce_repair (even though it is supposed to be depracated), multiple cache clears) but the one that seemed to work was updating EVA to the 7.x-1.x-dev version dated 9/19/2011. At any rate, my issue is fixed.

rHO

Abilnet’s picture

Abilnet commented
StatusFileSize
new installed_modules.gif2.51 MB

Thanks Ryan and rHOnDO, your help appreciated.

I, too, have installed Commerce with the "Kickstart" distro. However I do have a lot of additional modules installed (screenshot)

I'll try Commerce Repair, thanks rHO for the tip!

Abilnet’s picture

Abilnet commented

An update:

The error disappeared.

I believe my Token 7.x-1.0 had something to do with the problem, because when I'd upgrade Token -module to 7.x-1.1 everything seems to be working again.

rszrama’s picture

rszrama commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Alrighty, let's go ahead and close this unless we can come up with a consistent problem in Commerce itself; I'm glad the various module updates worked out. I'm guessing those modules interacted with the Entity API module in some way so as to prevent it from functioning properly here.

Abilnet’s picture

Abilnet commented

Got the Original Post -error (screen shot) again (this time the error appeared during check out).

I think an issue in EVA -module was the origin of the problem. After applying This Fix the error went away. Hopefully this helps someone in similar situation.

akamaus’s picture

akamaus commented

@Abilnet, Thanks! Recently I updated an outdated site and ran into the same problem. Installing dev version of eva instead of 1.1 as suggested in thread you gave a link to in #7 helped.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Closed (cannot reproduce) » Needs review
StatusFileSize
new commerce-customer-missing-profile-type-1577596.patch1 KB

Re-opening this, the actual reason for this is IMHO that we're trying to display a customer profile reference field for a customer profile type that does not exist anymore. Then it creates an empty new profile with no bundle and blows up.

While that is nothing that is supposed to happen, it can and protecting against it is easy enough. Patch attached, please test.

rszrama’s picture

rszrama commented
Status: Needs review » Fixed

Committed.

Status: Fixed » Closed (fixed)

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