Seems to be a persistant problem when logged in, but strangely not that fatal as it keeps cropping up just below the footer when I'm logged in to my live site, but doesn't show to anonymous users. White screen plus titular error message when attempting to run cron manually. It's supposed to run once a day on my site but doesn't seem to run at all, if the status report's "cron last run 1 week ago" or so is to be believed.

My dev site is running the -dev from 23 Dec 2010, problem persists. Line 7307 is:

$entity->{$info['entity keys']['id']} = $ids[0];

Ideas on where to look appreciated as I'm out :|

Thanks! :)

Comments

ryivhnn’s picture

ryivhnn commented

I suddenly have a metric buttload of extra information with the aforementioned error message. I'm guessing it has something to do with the fact I finally got round to installing xdebug. Currently have exactly nfi how to read these things never mind what to do about them, blatting it here so someone can tell me how to fix it or even how to read it if I don't figure it out eventually. The site is running D7rc4 (upgraded...or maybe sidegraded...from the -dev) and I think it's just a problem with that site (module conflict maybe, or something) as I haven't (yet) encountered much in the way of drama with another dev site running D7rc3. May turn out a clean install is the way to go. Anyway.

Call Stack: 0.0001 642672 
1. {main}() [...]/index.php:0 0.2075 29569888 
2. menu_execute_active_handler() [..]/index.php:22 0.2155 30798696 
3. call_user_func_array() [..]/includes/menu.inc:499 0.2155 30799032 
4. drupal_get_form() [..]/includes/menu.inc:0 0.2155 30799880 
5. drupal_build_form() [..]/includes/form.inc:188 0.2200 31200976 
6. drupal_process_form() [..]/includes/form.inc:350 0.2223 31257000 
7. form_execute_handlers() [..]/includes/form.inc:830 0.2224 31260448 
8. system_run_cron_submit() [..]/includes/form.inc:1390 0.2224 31260448 
9. drupal_cron_run() [..]/modules/system/system.admin.inc:1593 0.2254 31359712 
10. module_invoke_all() [..]/includes/common.inc:5029 0.2313 31386528 
11. call_user_func_array() [..]/includes/module.inc:817 0.2313 31386776 
12. field_cron() [..]/includes/module.inc:0 0.2314 31386824 
13. field_purge_batch() [..]/modules/field/field.module:191 0.2363 32017952 
14. EntityFieldQuery->execute() [..]/modules/field/field.crud.inc:1054 0.2366 32018848 
15. call_user_func() [..]/includes/entity.inc:1012 0.2366 32018880 
16. field_sql_storage_field_storage_query() [..]/includes/entity.inc:0 0.2368 32031512 
17. EntityFieldQuery->finishQuery() [..]/modules/field/modules/field_sql_storage/field_sql_storage.module:569 0.2385 32045512 
18. entity_create_stub_entity() [..]/includes/entity.inc:1185

Edit: recently learned how to read the debug thing (duh), and after comparing it with a site that works, it's likely the entity module that's causing dramas. Investigating.

ryivhnn’s picture

ryivhnn commented
Status: Active » Closed (fixed)
Donald.Cole’s picture

Donald.Cole commented
Status: Closed (fixed) » Active

I am asking to reopen this because I am experiencing the same issue. Cannot access empty property in [...]/includes/common.inc on line 7307

This began showing up after I updated the media module in response to a security issue. I am running this on my local machine using Aquia dev desktop. I am running Drupal 7.9, the Media version that I had was 7.x-1.0-beta4 and the available updates report indicated that there was a security issue. I updated to 7.x-1.0-rc2 and began receiving the same message above. My programming knowledge is limited so I do not know what to look for. I appreciate any help that someone can offer.

-enzo-’s picture

-enzo- commented

I've the same issue in Drupal 7.15 :S

marcingy’s picture

marcingy commented
Status: Active » Postponed (maintainer needs more info)

Please provide steps to recreate on a clean drupal install

jkingsnorth’s picture

jkingsnorth commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

There was no further response from the original poster so I'm going to close the issue for now. Please do reopen the issue if you still require assistance, with full instructions to recreate the error from a fresh installation of the latest version.