Failure to enable commerce_order_ui: Recoverable fatal error: Argument 2 passed to entity_views_field_definition() must be array

Hmm, it sounds like perhaps the Order Total price field wasn't properly created when the Order module was installed. Did you experience any white screen errors during installation? Also, if this is a new site, it would be much better to just use the Commerce Kickstart installation profile; it mimics a standard installation but enables all the Commerce modules and their dependencies during the normal installer, which uses a batch process to enable modules in order and avoid PHP errors during installation.

Try manually truncating your cache table.

I was experiencing similar errors, which ceased after I did that.

Ahh, sorry to hear it. Before going any further, make sure you've backed up your database unless you're already working on a dev copy of your existing site (recommended). rfay has developed a module to repair missing fields that should solve this issue for you: http://drupal.org/project/commerce_repair

I'm having this same error. It originally showed up (and after adding a couple of products) killed the whole site. Couldn't access any pages or use drush. I've ripped out the module and used this: http://drupal.org/project/registry_rebuild (for anyone else in the same place) to recover my site.

Now I just can't get commerce (and it's 20 sub modules) to install correctly. I usually get about 3 in before this error starts back in. I've re-stripped out the module... dropped the tables. I'll try truncating the cache tables on this next round. I'm also running the latest versions of everything.. completely up to date.

Matt, when you went through the install, did you try to use the Commerce Repair module? And were you on 1.1 or 1.2? You might try using the 1.x-dev.

Ryan do you know if there is a command to run the repair in drush? I can't navigate through the site to actually run the repair from the actual UI because the site is throwing this error on every page.

I'm not sure if it supports drush or not - rfay is a fan of it, though, so I wouldn't be surprised. I'd ask in http://drupal.org/project/issues/commerce_repair.

Thanks

@mattsmith3, I think you need a new issue, and please report the exact results you have. I doubt they're exactly the same as this old issue. Please post the link to the new issue here.

It *does* seem like you might have an old version of Entity module. I'm sure you know that Commerce depends on Entity, Rules, and Views, and they have to be updated with the various Commerce modules.

It doesn't actually make any sense that if you delete all commerce tables you wouldn't be able to install. However, you may be missing some field tables. #858722-61: Cannot reinstall Commerce modules after uninstall due to field deletion failure has a brute-force uninstall script that might point out to you something you failed to do. (That is old and hasn't been revisited, so you get what you pay for :-)

I'm having the same error as mattsmith #7. Like him it originally showed up, and after adding the product UI module, it killed the whole site. Cannot access any pages or use drush. Before the final crash, I also tried the commerce_repair module, without any results.

Please refer to rfay's comments above; there are good reasons to believe the initial issue here has been dealt with through other module updates, but if not, let's have a separate issue that outlines the bug with steps to reproduce the issue in a clean install of Drupal Commerce. For issues like this, we can't even begin to debug the problem until we can reproduce it locally.

This bug is still present, it's very hard to track down, however. I can make it happen consistently on our dev site, but getting it to appear from an installation created from scratch is proving to be difficult.

There is one strong correlation, however: the bug only appears when we have EVA already installed. Then when the Order UI (edit: apologies, I meant Order module) module is enabled the bug is triggered, specifically the problem happens when entity_views_field_definition() is called for the commerce_order_total field.

Side note: I've tried enabling each module one-by-one in case the issue is anywhere lower down the dependency chain.

So this is definitely a bug, however I'm guessing it's just normal priority since it can be worked around by disabling EVA before installing Commerce.

What I'm wondering is: do all the other people with this issue have EVA installed?

EDIT: just to note, the reason I re-opened this is to ask the other people in the issue whether they had EVA installed, too. If I find a way to reproduce this bug consistently, I'll open a new issue.

Ok, let's leave this as a postponed support request then and see if anyone else chimes in. I doubt it's gonna happen, though... resurrecting old issues rarely results in new information.

I have been looking into this issue with Liam, and I've tracked the problem as far as commerce_order_entity_property_info_alter() in commerce_order.info.inc. On the installation with EVA enabled, $properties['commerce_order_total'] is not set, which is causing the null value to be set in $info, ultimately resulting in the fatal error.

$info['commerce_order']['properties']['commerce_order_total'] = $properties['commerce_order_total'];

I can't figure out why EVA would be causing the issue, but it seems like the culprit based on our testing. I'm going to investigate further, but if this triggers any thoughts from the experts, those thoughts are very welcome. :)

It turns out the field wasn't being created when the order module was enabled. If you check whether the properties are set in commerce_order_entity_property_info_alter() before moving them to the commerce_order properties, the problem disappears. I'm still not sure why the problem is occurring in the first place, but this seems to be one solution.

if (isset($properties['commerce_line_items'])) {
  $info['commerce_order']['properties']['commerce_line_items'] = $properties['commerce_line_items'];
}
if (isset($properties['commerce_order_total'])) {
  $info['commerce_order']['properties']['commerce_order_total'] = $properties['commerce_order_total'];
}

Think I have a set of steps to reproduce this, so have created issue: #1871832: Conflict with Entity Views Attach (EVA)

Lucas, please could you try to repeat my steps in the other bug report and reply (in the other report) with the result? Just want to make sure what I did wasn't a fluke. :)

I'm guessing we can close this as a duplicate.

Issue #1509994: Missing entity property info results in notices / WSOD / fatal errors during installation looks very much similar to this one - and has a fix.

Patch from #17 of that issue helped.

I tried out the latest dev version of Commerce. I was able to install and enable all sub modules with 1.4+28...no issues. See my comment on http://drupal.org/node/1509994. Sadly, after posting this I tried the install on my real local dev site, rather than the fresh sandbox site (where it worked fine) and it broke it. Still working on it.

If this is a new site, why not try Commerce Kickstart 1.x?

Mystery solved!!!! It is definitely a conflict with the Eva module. Everything was perfect after disabling it.
I saw the posting earlier where someone was having that same eva issue, and I disabled it locally. However at the time I began having fatal errors thrown by the lack of resources settings in my local dev site "my.ini" file (http://drupal.org/node/259580), and thought the eva thing was not helping.
So, I had 2 sets of problems going and had to peel the onion. It worked locally once I got past the resources issue, then had the original problem (this issue queue) on the staging site. Why? Because I had not disabled eva on the remote dev site. Dang.
Anyway, the eva module was not being used for much, so it goes, in favor of Commerce.
Great module! Nice job. I hope this helps anyone else who might have either or both of these issues.
BTW, KickStart is wonderful. I did all my "studying" on it, before attempting Commerce on the existing site.
Thank you, many times over.