After updating commerce-kickstart 2.0rc4 to 2.1 I get different errors. When I'm logged in as admin, I get the following on every non-admin page:
EntityMetadataWrapperException: Unable to get the data property data as the parent data structure is not set. in EntityStructureWrapper->getPropertyValue() (Zeile 442 von /Applications/MAMP/htdocs/profiles/commerce_kickstart/modules/contrib/entity/includes/entity.wrapper.inc).
As anonymous user I don't get this error and I can see the homepage and all product pages.

When I'm not logged in I get an error when I want to add s.th. to the cart:
DatabaseTransactionOutOfOrderException: in DatabaseConnection->rollback() (Zeile 1052 von /Applications/MAMP/htdocs/includes/database/database.inc).

I tried to find help on drupal.org, but none of the posted issues seem to fit. I'm stuck and need help on this one. Thanks.

Comments

jwjoshuawalker’s picture

This may not help your situation, but I just dealt with the DatabaseTransactionOutOfOrderException: part you mentioned, I see a few other posts talking about it, but my cause was different from those.

I did a back trace which lead me to commerce/modules/order/includes/commerce_order.controller.inc, and because of the custom checkout pane/page setup I had, somehow the Billing & Shipping information was getting out of sync.

I rearranged the order of my panes and switched to the 7.2-dev version of commerce_shipping and all was good.

I would suggest as a place to start, go into database.inc the line before exception gets thrown, and drop a back trace in there, like:
<?php print debug_print_backtrace(); ?>

This will let you at least track the exception back to it's source and probably give you a clue (as it did in my situation) on where to start looking.

bojanz’s picture

Category: bug » support
Status: Active » Fixed

Unfortunately, this is not something we'd be able to debug without indepth access to your setup, and personal time which we don't have.
You will need to find what it is in your setup (modules, server setup) that could be causing something like this, and go from there.
Let us know if you learn anything interesting.

Status: Fixed » Closed (fixed)

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