Closed (cannot reproduce)
Project:
Commerce Core
Version:
7.x-1.4
Component:
Order
Priority:
Major
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
11 Jun 2011 at 10:56 UTC
Updated:
16 Jan 2013 at 20:24 UTC
Just updated to the latest dev version and get the following fatal error
Fatal error: Class 'DrupalCommerceEntityController' not found in .../sites/all/modules/commerce/modules/order/includes/commerce_order.controller.inc on line 12
Comments
Comment #1
dwkitchen commentedThis is the same for beta4, reverted to beta3
Comment #2
hubrt commentedexactly the same here.
Comment #3
roam2345 commentedyup and another
was on a dev version june 9 might account for my error slightly different.
then going to update.php and running the update I get
Comment #4
rszrama commentedDid you guys run update.php?
Comment #5
damien tournoud commentedYou will need to run update.php and update the Entity and Rules modules to the latest -dev.
Comment #6
roam2345 commentedYup that worked.
Needed updates to entity_api and rules dev releases and it worked.
Comment #7
damien tournoud commentedThe release notes have been updated to make it clearer that you need to update Rules and Entity.
Comment #8
damien tournoud commentedComment #9
JohnDoranNY commentedI ran update and it gives me errors:
The following updates returned messages:
An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: http://adb.johndoran.net/update.php?id=20&op=do StatusText: parsererror ResponseText: Fatal error: Call to undefined function entity_rules_events_variables() in /home/content/21/7420121/html/adb/sites/all/modules/commerce/modules/payment/commerce_payment.rules.inc on line 23
And the error page reported:
commerce_customer module
Update #7000
•Role and custom View permissions updated for order entity management. Access checks in modules and permissions on default Views must be updated manually.
And any page I try to access gives me just "Fatal error: Call to undefined function entity_rules_events_variables() in /home/content/21/7420121/html/adb/sites/all/modules/commerce/modules/payment/commerce_payment.rules.inc on line 23"
edit
I rolled back the database... applied the rules patch... reuploaded the commerce and rules and went to update and still receive the errors:
The update process was aborted prematurely while running update #7100 in commerce.module. All errors have been logged. You may need to check the watchdog database table manually.
•Front page
•Administration pages
The following updates returned messages
The update process was aborted prematurely while running update #7100 in commerce.module. All errors have been logged. You may need to check the watchdog database table manually.
commerce_product module
Update #7101
•Role and custom View permissions updated for product entity management. Access checks in modules and permissions on default Views must be updated manually.
commerce_order module
Update #7104
•Role and custom View permissions updated for order entity management. Access checks in modules and permissions on default Views must be updated manually.
commerce_cart module
Update #7100
•All eligible product attribute fields have been updated to continue using the attribute selection widget.
Re-Edit
Okay, sorry, ,I think the problem was the Commerce_Shipping module... I disabled it through the database, retried the whole process from scratch, and now it seems to work.
Comment #10
rfayI got bit by this.
Seems like we can do better.
Comment #11
rfayIf your registry gets hosed and you can't get past this (as happened to me) you can rebuild your class registry with Registry Rebuild.
First, of course, follow the instructions above and get the current entity and rules in there.
Comment #12
guillaumev commentedHi,
A new error while trying to update to beta4:
I have various entity and rules updated to the latest dev version, but I have various commerce modules activated (commerce stock, commerce shipping, commerce paypal etc...)
I'm investigating to try to find the cause...
Comment #13
rszrama commentedIt's not a new error - you just need to clear your cache (this should be resolved by running update.php). Be sure you read the release notes for that update.
Comment #14
guillaumev commentedMy bad ! I had not cleared the cache after the install of rules and entity... After clearing the cache, everything worked fine...
Comment #16
jlporter commentedI just did a new install and hit this bug. I updated the relevant modules(entity/rules) to no avail, I couldn't hit update.php, and even drush cc all failed. I tried disabling the only customer module I had enabled and was still hitting the 500.
I worked around it by adding to commerce/modules/customer/includes/commerce_customer_profile.controller.inc
include_once('sites/all/modules/commerce/includes/commerce.controller.inc');
I know it's an ugly hack, but I'm able to finally move on. There were no pending db updates(this is a fresh install).
If I remove my hack I get 500'ed
Comment #17
rfayYou should probably use Registry Rebuild to get your site back in action. I imagine your registry table has been messed up, especially if you hadn't updated for awhile. There was some serious confusion about a month ago with Entity module.
Comment #18
rszrama commentedGive that registry rebuild a shot. I'm hesitant to just reopen this issue here when it's not necessarily a Commerce issue.
Comment #19
crystaldawn commented#16 is correct, his fix works. This needs to be fixed properly in the update portions. I had his exact issue with the newest version (drush updated from something seriously old, to the newest and ran into this issue) as of this writting and his fix seemed to work. Rebuilding the registry does nothing to fix this issue.
Comment #20
crystaldawn commentedIt turns out that the update process with Drush (I have no idea how) had managed to disable the Commerce module yet none of the modules that depended upon Commerce were disabled. Go figure. GREMLINS I tell ya! Gremlins! Anyway, for me at least, this is why the file was coming up missing. I wouldnt know how to reproduce this other than install a really old version and see if it upgrades I guess.