Closed (fixed)
Project:
Ubercart
Version:
7.x-3.1
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
10 May 2012 at 02:57 UTC
Updated:
3 Jul 2013 at 18:50 UTC
Jump to comment: Most recent file
I can't startup my system
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | 1570038-5.patch | 395 bytes | theladebug |
Comments
Comment #1
tr commentedThat class resides in uc_order/uc_order.info.inc, so make sure the include file is present and clear your caches. If you've upgraded your version of Ubercart, be sure to run update.php. Rebuild your class registry if necessary with http://drupal.org/project/registry_rebuild
Comment #2
socialnicheguru commentedthanks. I have been going crazy all day with this
Comment #4
theladebug commentedComment #5
tr commented? If you expect help, I suggest you provide some information. At a minimum, say what you've tried, which better include the advice given in #1 ...
Comment #6
theladebug commentedThis is still happening, along with the salesforce module in my case. It's because the entity metadata file isnt listed in the uc_order.info file.
Attached is a patch for it.
Comment #7
theladebug commentedSorry TR, I could have probably re-opened and patched at the same time :)
Comment #9
longwaveThis isn't an Ubercart issue. As I described #1989168: Fatal error: Class 'UcOrderProductMetadataController' not found in .../sites/all/modules/entity/entity.info.inc, the Salesforce module is calling entity_entity_property_info() when this function should be called as a hook, which would automatically include the right file. This same issue would affect other modules that implement hook_entity_property_info() and put them in a .info.inc file. Ubercart uses the class in question, and does not suffer from this error, because it uses the hook system correctly.
Comment #10
longwaveHaving said that I guess this wouldn't hurt, as class files are autoloaded as needed. Committed to 7.x-3.x.
Comment #11
theladebug commentedThanks for clarifying, hopefully adding it to the .info file will save you some headaches in the future when other modules make the same mistake and throw a similar error message.
Before I committed this, I double checked some other modules which were working properly in my situation and the only difference was that the other modules had this file listed in their .info files, so it seems like this helps accomodate other modules which fail to use the entity hooks properly.