Fatal error: Cannot access empty property in field.attach.inc

1. set to garland before update
2. Fatal error: Cannot access empty property in modules/field/field.attach.inc on line 317 isn't error isn't a critical error, unless you sure you have lost data.
3. Undefined index, it's can be normal issues, never broken your daily usage

#2: #1015042: Simpletest tables are not created

Needs more info.. like fresh D6.20 to fresh D7, to see if same problem.. so we can know that come from modules or core

@mollerz,
bug report should always test against Dev version.

"•Notice: Undefined property: stdClass::$content in include() (line 10 of /home/www/fuckd.dk/themes/garland/block.tpl.php)."

It's error in garland block.tpl.php, which this tpl is not there by default. so I guess there is an old file and old codes inside the file cause the problem.

This is difficult to track down.

@mollerz and anyone getting similar errors :
- Please apply the debug patch attached below. It will hide (but not fix) the fatal error, and more importantly display some debug information that should help pinning this down.
- Report the output here (might be large, please upload in a .txt file)

[edit : see patch #23 instead]

Applied patch, went to content/media tab and got this error:
Fatal error: Cannot access empty property in /drupal7/modules/field/field.attach.inc on line 725

The original error was:
Fatal error: Cannot access empty property in /drupal7/modules/field/field.attach.inc on line 677

Attached the requested debug info.

You can find me on irc if you want more help.

Same error like #10

Do all of those who are seing this error have media.module installed?

Try to disable it...

Yes it is related to the media module. (at least for me)
I'm here via #1015580: Media entities : Cannot access empty property in field.attach.inc line 677

Thanks folks.

#10 and #11 are both caused by Media module calling Field API with $entities where we cannot extract a bundle. I bumped #1015580: Media entities : Cannot access empty property in field.attach.inc line 677 back to the Media issue queue.

I'd be interested to get the same data from @mollerz, since his case doesn't seem to involve Media module.

More generally, those errors are bound to come back on a regular basis (modules handing ill-formed entities without a bundle to the Field API).

We don't babysit broken code, but as is, those cases trigger cryptic errors in Field API and will flood the core queue while the error lies upstream. Same thing happened in CCK, until we added an explicit check to silently bypass nodes without a 'type'.

Pondering for now :
When those cases happen
- break with a fatal error / an exception, or fail silently ?
- how do we provide meaningful info on the actual source of the error - at least we'd need the entity type, possiby the callstack.

I get the exact same errors as the initial poster, after an upgrade from 6.20 to 7.0. I only have Drupal 7.0 core installed, i.e. no contributed modules.

@JackLynch : then could you follow the instructions in #9 ? Would help us identify the issue. Thanks !

Subscribing. I'm going to try and follow the #9 instructions...but I've never applied a patch before so we'll see what happens. Thanks

@mollerz : sorry, dropped off my radar.

It's strange that you still get the error. The debug patch in #9 should "hide" it and display debug message at the top of the 'content' area of the page instead.
Can you manually double check in the code the patch got applied correctly ?

Other than that, you can send me the url of the live site through my contact form (along with the url of a page triggering the error) ?

I'm getting the same error as well, after an upgrade from 6 to 7. I hope I applied the patch in #9 correctly, as I do it manually. But I get:

Fatal error: Cannot access empty property in /mysite.com/modules/field/field.multilingual.inc on line 276

OK, there are many places where an incoming $entity without a bundle property can break.
We need to catch those earlier on.

@mollerz, EmpireNM, and anyone getting similar errors :
Can you try with the attached debug patch instead ? (if you applied patch #9 previously, you probably want to revert it, but it makes no real difference). This should break with an error message providing information on where the malformed $entity object comes from.

If the error message mentions "entity type: media", then head over to #1015580: Media entities : Cannot access empty property in field.attach.inc line 677.
If the entity type is something else, please report here.

Notice: Undefined index: field_name in field_attach_load() (line 673 of /Users/biss/Sites/drupal7/modules/field/field.attach.inc).
Notice: Undefined index: field_id in field_attach_load() (line 674 of /Users/biss/Sites/drupal7/modules/field/field.attach.inc).
Notice: Undefined index: field_name in field_attach_load() (line 673 of /Users/biss/Sites/drupal7/modules/field/field.attach.inc).
Notice: Undefined index: field_id in field_attach_load() (line 674 of /Users/biss/Sites/drupal7/modules/field/field.attach.inc).
No modules selected.
Notice: Undefined index: field_name in field_attach_load() (line 673 of /Users/biss/Sites/drupal7/modules/field/field.attach.inc).
Notice: Undefined index: field_id in field_attach_load() (line 674 of /Users/biss/Sites/drupal7/modules/field/field.attach.inc).
Notice: Undefined index: field_name in field_attach_load() (line 673 of /Users/biss/Sites/drupal7/modules/field/field.attach.inc).
Notice: Undefined index: field_id in field_attach_load() (line 674 of /Users/biss/Sites/drupal7/modules/field/field.attach.inc).
No modules selected.
Notice: Undefined index: field_name in field_attach_load() (line 673 of /Users/biss/Sites/drupal7/modules/field/field.attach.inc).
Notice: Undefined index: field_id in field_attach_load() (line 674 of /Users/biss/Sites/drupal7/modules/field/field.attach.inc).
Notice: Undefined index: field_name in field_attach_load() (line 673 of /Users/biss/Sites/drupal7/modules/field/field.attach.inc).
Notice: Undefined index: field_id in field_attach_load() (line 674 of /Users/biss/Sites/drupal7/modules/field/field.attach.inc).
Notice: Undefined index: field_name in field_attach_load() (line 673 of /Users/biss/Sites/drupal7/modules/field/field.attach.inc).
Notice: Undefined index: field_id in field_attach_load() (line 674 of /Users/biss/Sites/drupal7/modules/field/field.attach.inc).
Exception: Encountered an entity without a bundle property (entity type: media, callstack: entity_extract_ids, field_attach_load, attachLoad, load, entity_load, media_load, media_save_attached_file, media_file_update, call_user_func_array, module_invoke_all, [...]). in entity_extract_ids() (line 7369 of /Users/biss/Sites/drupal7/includes/common.inc).

@kannary : thanks. In your case that's dealt with in #1015580: Media entities : Cannot access empty property in field.attach.inc line 677.

I edited the instructions in #23. We're searching whether this happens on other entity types than 'media'.

Thanks for the help yched,

Here's the error I got after applying your new patch:

Exception: Encountered an entity without a bundle property (entity type: node, callstack: entity_extract_ids, _field_invoke_multiple, field_attach_prepare_view, node_build_content, node_view, _node_index_node, node_update_index, call_user_func_array, module_invoke, search_cron, [...]). in entity_extract_ids() (line 7300 of /mysite.com/includes/common.inc).

Thanks yched

@mollerz: probably something wrong with the way you edited the function, although I can't spot it in the code you pasted above. Here is the patched version of the function.

@EmpireNM : thanks, will look into this

@mollerz: thanks. So your case is the same as the one reported by @EmpireNM in #26.

The issue here is in fact completely unrelated to Field API - it so happens that Field API is the only part that severely breaks on it.

_node_index_node() tries to manipulate a $node that hasn't loaded properly. In fact, the "Trying to get property of non-object in _node_index_node()" error on line 2624 (which tries to access $node->changed) seems to indicate that the node_load() on the previous line returned FALSE.

Now, what's strange is that the nid that we try to load comes from a direct query on the {node} table in node_update_index(). So the nid should definitely exist.

Debug this is a little tough:
- You guys would need to identify the nid that fails to load correctly, for instance by modifying the beginning of _node_index_node() this way :

function _node_index_node($node) {
  $nid = $node->nid;
  $node = node_load($nid);
  if (!$node) {
    debug(t('Failed to load nid @nid', array('@nid' => $nid));
    return;
  }

  // (the rest of the function)
}

- Then we need to find what's wrong with the node(s) - first of all, check if the corresponding records in the {node} table look wrong.

- Then we need to identify what causes the wrongness, and whether _node_index_node() should be bullet proofed against that.

Anyway, bumping this thread out of the Field API queue.

I'll open a separate issue to get the patch in #23 committed, so that Field API fails in a tale-telling way when it is fed with an invalid $entity object.

#1067750: Let Field API fail in a tale-telling way on invalid $entity

@mollerz: the interesting part is the "Failed to load nid 21" message.
Something's wrong with your node 21. Can you take a look at the corresponding record in the 'node' table (using phpMyAdmin or equivalent), and see if you notice something off ?

type: Blog

'Blog' or 'blog' ? If that's capitalized, that doesn't look right.

Also: maybe check the node_revision table ?

No correspondig record in the node_revision table is wrong.

Deleting the record for node 21 is probably the best thing to do. It doesn't provide any clue as to what put your db in that state, though.

It would be interesting to check if you have other broken nodes in there :
SELECT * FROM node WHERE nid NOT IN (SELECT nid FROM node_revision)
(in phpMyAdmin)

I followed the instructions in #23 and get:

Exception: Encountered an entity without a bundle property (entity type: comment, callstack: entity_extract_ids, _field_invoke_multiple, field_attach_prepare_view, comment_view_multiple, comment_node_update_index, call_user_func_array, module_invoke_all, _node_index_node, node_update_index, call_user_func_array, [...]). in function entity_extract_ids() (line 7302 in /home/public/includes/common.inc).

Now i have fatal error on every page.
Cannot access empty property in /home/public/modules/field/field.attach.inc on line 317

I get other errors form my site on localhost (winXP):

Notice: Undefined variable: key in comment_prepare_thread() (line 897 of D:\sites\public\modules\comment\comment.module).
Strict warning: Creating default object from empty value in comment_prepare_thread() (line 897 of D:\sites\public\modules\comment\comment.module).
Notice: Undefined property: stdClass::$node_type in entity_extract_ids() (line 7290 of D:\sites\public\includes\common.inc).
Warning: Cannot modify header information - headers already sent by (output started at D:\sites\public\includes\common.inc:2561) in drupal_send_headers() (line 1040 of D:\sites\public\includes\bootstrap.inc).
Exception: Encountered an entity without a bundle property (entity type: comment, callstack: entity_extract_ids, _field_invoke_multiple, field_attach_prepare_view, comment_view_multiple, comment_node_update_index, call_user_func_array, module_invoke_all, _node_index_node, node_update_index, call_user_func_array, [...]). in entity_extract_ids() (line 7302 of D:\sites\public\includes\common.inc).
The website encountered an unexpected error. Please try again later.

Notice: Undefined index: field_name in field_attach_load() (line 673 of /xxxxxxxxx/html/modules/field/field.attach.inc).

Notice: Undefined index: field_id in field_attach_load() (line 674 of /xxxxxxxxx/html/modules/field/field.attach.inc).

Checking the database with phpMyadmin and SELECT * FROM node WHERE nid NOT IN (SELECT nid FROM node_revision) returns no rows, so the database is not corrupt, yet I stil get the error

Now when I go to Content>Media I get

Fatal error: Cannot access empty property in /xxxxxxxxx/html/modules/field/field.attach.inc on line 677

Drupal 7.0 Media Module

Following http://drupal.org/node/1015580 now. seems to be the issue

I got this error after trying to access a node with a comment. I do NOT have Media module installed. And, the error is occurring on a fresh D7 release install, with few contrib modules. Breaks the whole node. Had to rollback the freakin' database to resolve the problem. I previously reported a problem with D7 core comment module (issue pretty much ignored).

@greta_drupal : please
- apply patch #23 above (or replace the entity_extract_ids() function with the code provided in #29),
- and report the error message you get (the one that starts with "Exception: Encountered an entity without a bundle property...")

Complete newbie here so please bear with me.
I'm using 1and1 hosting to host my Drupal 7 site. I am trying to enable users to post audio recordings of our general meetings. I installed Media 7.x-1.0-beta3 and Audiofield 7.x-1.0-beta1. I am getting similar errors as above.
When I click on the 'Media' tab of the 'Content' page I get:

Fatal error: Cannot access empty property in /homepages/19/d311504504/htdocs/live/dd/modules/field/field.attach.inc on line 677

clicking the back button gives:

Notice: Undefined index: field_name in field_attach_load() (line 673 of /homepages/19/d311504504/htdocs/live/dd/modules/field/field.attach.inc).
Notice: Undefined index: field_id in field_attach_load() (line 674 of /homepages/19/d311504504/htdocs/live/dd/modules/field/field.attach.inc).
Notice: Undefined index: field_name in field_attach_load() (line 673 of /homepages/19/d311504504/htdocs/live/dd/modules/field/field.attach.inc).
Notice: Undefined index: field_id in field_attach_load() (line 674 of /homepages/19/d311504504/htdocs/live/dd/modules/field/field.attach.inc).

I saw the patch above in post #23 but haven't the slightest clue how to apply it. I saw the page 'http://drupal.org/patch/apply' but don't know how to get a command prompt, is there another way?

thanks...

@Mick Cagney : you want to read this issue : #1015580: Media entities : Cannot access empty property in field.attach.inc line 677

In short : you need to install the current Media 7.x-1.x-dev, this should be fixed in there.

I had the same problem as @greta_drupal in #43 after an upgrade from 5 to 6 to 7.

The comments table looks fine except the language is not set to "und", it is just blank. Deleting all comments allows the node to be displayed again, and I can add a comment (as user 1). Adding a comment as anonymous adds the comment to the database table, but the comment does not appear in the approval queue. The local menu task for Unapproved comments shows the correct comment count (2) but then states "No comments available". There is also a pager with 79 pages. The error log shows Notice: Undefined index: group in _date_views_fields() (line 61 of E:\www\sites\all\modules\date\date_views\includes\date_views_fields.inc). Heading to comment/COMMENT-ID/edit returns 404 not found.

After an hour or two of debugging I found that the anonymous user had a UID of 443 instead of 0. This is quite common when moving databases around. Solution: edit the users table and set the anonymous UID to 0.

I got a separate report from markfinney by my contact form, exactly the same as @Chi's #41,

Exception: Encountered an entity without a bundle property (entity type: comment, callstack: entity_extract_ids, _field_invoke_multiple, field_attach_prepare_view, comment_view_multiple, comment_node_update_index, call_user_func_array, module_invoke_all, _node_index_node, node_update_index, call_user_func_array, [...]).

(see #41 for the exact sequence of errors)

This happens during the indexation of contents for the search index, which usually happen on cron, but might randomly happen on regular page views, since cron tasks are automatically triggered from time to time if the server crontabs are not configured.

The error in this case seems to lie in comment_node_update_index() :

    if ($node->comment && $cids = comment_get_thread($node, $mode, $comments_per_page)) {
      $comments = comment_load_multiple($cids);
      comment_prepare_thread($comments);
      $build = comment_view_multiple($comments, $node);
      return drupal_render($build);
    }

For some reason the comment_load_multiple($cids) call fails to load the comments and returns NULL, which the rest of the code doesn't expect, and triggers all the chain of errors reported.

Now, markfinney tells me that the comments had been manually imported in his database from an earlier core version, so I'm not sure we can call a core bug in his case. I'd be interested to know if that was also the case for @Chi ?

+ we'd really need to get #1028230: Fatal error: Cannot access empty property in field.attach.inc in. This thread is hardly manageable, since people rightfully report the same error for various and completely unrelated underlying bugs.

In my case comments also had been imported from an earlier core version via custom PHP-CLI script.

I've fixed it with this code in comment_prepare_thread(). But now after rollbacking I cannot reproduce bug.

   // The final comment must close up some hanging divs
-  $comments[$key]->divs_final = $divs;
+  if (isset($key)) {
+    $comments[$key]->divs_final = $divs;
+  }

Thanks for the feedback, @Chi. I'm not sure this qualifies as a core bug, then. I guess we'd want to find out exactly what's wrong with your manually edited db that causes comment_load_multiple() to fail, but I'm not sure I can help with that.

I'm not even sure we'd want to make that code snippet stronger when the comment_load_multiple() fails. At least the errors act as a smoke sign that something is wrong in the db, failing silently would just hide the problem.

Then I guess we have covered all cases of "Cannot access empty property in field.attach.inc" reported so far... We still really need #1028230: Fatal error: Cannot access empty property in field.attach.inc so that possible later reports can be easily sorted in separate issues.

This is perhaps a silly example, but it fixed my problem with the"Fatal error: Cannot access empty property in modules/field/field.attach.inc on line 317"

I had 3 content types in same display in views, and one field was not in all of the content types. Silly mistake, which took up a lot of time.

@havard : which version of views are you using ?

@yched, views dev from april 25

@havard : odd - Views listing nodes of several different types, where some fields are not present on all node types, is definitely a valid case and should work flawlessly. I don't get any "Fatal error: Cannot access empty property in field.attach.inc" when I test such a case.

I am also having this error on 7.0, applied the patch refered on the #23 and my errors were:

Notice: Trying to get property of non-object in block_block_view() (line 246 of /home/uranus_root/bestlovepoems.net/modules/block/block.module).

Notice: Trying to get property of non-object in block_block_view() (line 246 of /home/uranus_root/bestlovepoems.net/modules/block/block.module).

Notice: Undefined variable: key in comment_prepare_thread() (line 897 of /home/uranus_root/bestlovepoems.net/modules/comment/comment.module).

Notice: Undefined property: stdClass::$node_type in entity_extract_ids() (line 7286 of /home/uranus_root/bestlovepoems.net/includes/common.inc).

Warning: Cannot modify header information - headers already sent by (output started at /home/uranus_root/bestlovepoems.net/includes/common.inc:2561) in drupal_send_headers() (line 1040 of /home/uranus_root/bestlovepoems.net/includes/bootstrap.inc).

Exception: Encountered an entity without a bundle property (entity type: comment, callstack: entity_extract_ids, _field_invoke_multiple, field_attach_prepare_view, comment_view_multiple, comment_node_update_index, call_user_func_array, module_invoke_all, _node_index_node, node_update_index, call_user_func_array, [...]). in entity_extract_ids() (line 7298 of /home/uranus_root/bestlovepoems.net/includes/common.inc).

Error
The website encountered an unexpected error. Please try again later.

If I apply instead the patch on #9, what I get is:

Notice: Trying to get property of non-object in block_block_view() (line 246 of /home/uranus_root/bestlovepoems.net/modules/block/block.module).

Notice: Trying to get property of non-object in block_block_view() (line 246 of /home/uranus_root/bestlovepoems.net/modules/block/block.module).

Fatal error: Cannot access empty property in /home/uranus_root/bestlovepoems.net/modules/field/field.multilingual.inc on line 276

PS: Is there a way of hidding the message "Fatal error: Cannot access empty property in /home/uranus_root/bestlovepoems.net/modules/field/field.attach.inc on line 317", while the problem is not solved? None of the patches or selecting "Error messages to display=none", hides this erros to my users... :(

@mcduarte2000 : all similar reports so far happened on sites where the comment table has been manually tampered with (comments manually imported in the db, for instance). See #48 #50 #52. Is that also the case for your site ?

@yched: No, I upgraded from a previous version of Drupal and I didn't have this error after the upgrade (soon after the 7.0 launch), it appeared recently. Also, I get this error on every page of the site, even on administration pages and pages without any comment...

@yched : One of my content types was a group content type and the field that caused the error was group audience. The error disapeared immediently when I deleted this field.

@havard : then it's probably something wrong / not bulletproof in og_field_formatter_view().
You should probably report that case in the OG queue.

Following the suggestion in #42 of

SELECT * FROM node WHERE nid NOT IN (SELECT nid FROM node_revision)

returned several nodes which I deleted and the errors went away. Thanks.

I just tried that, but I just get "MySQL returned an empty result set (i.e. zero rows).", so its not my problem...

Hi
Drupal 7.2 upgraded from 6.22.
PHP 5.3.x

I also see thins when I enable "group by" in Views 3.dev. (3 June), trigger a PHP Fatal error: Cannot access empty property in /drupal-7.2/modules/field/field.attach.inc on line 317. Turning off the Media-module (not uninstalling) changes nothing.

SELECT * FROM node WHERE nid NOT IN (SELECT nid FROM node_revision) returns null.

Applied patch from #23:

Notice: Undefined index: field_author_name_nid in view->fix_missing_relationships() (line 395 of  /drupal7_versjon/drupal-7.2/sites/all/modules/views/includes/view.inc).
Notice: Undefined index: field_node_ref_nid in view->fix_missing_relationships() (line 395 of  /drupal7_versjon/drupal-7.2/sites/all/modules/views/includes/view.inc).
Notice: Undefined index: in _field_invoke_multiple() (line 299 of  /drupal7_versjon/drupal-7.2/modules/field/field.attach.inc).
Notice: Undefined index: in _field_invoke_multiple() (line 299 of  /drupal7_versjon/drupal-7.2/modules/field/field.attach.inc).
Notice: Undefined index: in _field_invoke_multiple() (line 299 of  /drupal7_versjon/drupal-7.2/modules/field/field.attach.inc).
Notice: Undefined index: in _field_invoke_multiple() (line 299 of  /drupal7_versjon/drupal-7.2/modules/field/field.attach.inc).
Notice: Undefined index: in _field_invoke_multiple() (line 299 of  /drupal7_versjon/drupal-7.2/modules/field/field.attach.inc).
Notice: Undefined index: in _field_invoke_multiple() (line 299 of  /drupal7_versjon/drupal-7.2/modules/field/field.attach.inc).
Notice: Undefined index: in _field_invoke_multiple() (line 299 of  /drupal7_versjon/drupal-7.2/modules/field/field.attach.inc).
Notice: Undefined index: in _field_invoke_multiple() (line 299 of  /drupal7_versjon/drupal-7.2/modules/field/field.attach.inc).

This did it for me! Thnx, found an obsolete node

Moving back to 8.x, we fix bugs in the highest affected version then backport.

subscribing

Subscribing. I'm in the same boat as mcduarte2000. I made the change in #51 and that has gotten my site (admin pages, nodes, etc) back but I'd like to get to the bottom of this issue.

So, as a summary : those errors happen when some code somewhere calls Field API on a malformed $entity object (no 'bundle' property). There's nothing Field API can do about the error, the calling code needs to be identified and fixed.

Latest D7-dev (post 7.7) includes #1067750: Let Field API fail in a tale-telling way on invalid $entity, which now dies with an Exception when such error conditions happen.
The exception message includes the type of entity that creates the error. We'd still need #1158322: Add backtrace to all errors to be able to point the erroneous calling code precisely, but at least the entity type can help direct the bug report to the faulty module.

Therefore, putting this thread to rest.

I am sorry for reopening this thread, but I can't find ANY information anywhere online how the error can be resolved. I have upgraded from D6.24 to D7.12 (the same happened when I tried to upgrade from D6.22 to D7.10).

This is what I get on a node that containes one comment:

Notice: Undefined variable: key in comment_prepare_thread() (line 900 of /home1/mysite/public_html/test7/modules/comment/comment.module).
EntityMalformedException: Missing bundle property on entity of type comment. in entity_extract_ids() (line 7501 of /home1/mysite/public_html/test7/includes/common.inc).

If a node contains more than one comment, no error is shown, but only one comment is displayed, others are not.

Before upgrading I disabled and uninstalled all non-core modules.

Trying to fix this error, I uninstalled the comment module and installed it back again. But when anonymous comment is posted, the same error occurs again: the page is broken and the abovementioned error is displayed.

Is there anyway how this could be resolved? I would be very grateful for any assistance! Thanks!

#72: I recommend opening a separate issue, with explicit steps to reproduce your issue, starting from "Install Drupal 7.x." If one of the steps to reproduce is to install a contributed module, then the issue should be filed against that module's queue.

Just want to provide some extra insight into this issue. We experienced a similar problem, but when utilising the search module.

Searches on our site for certain terms were giving the same error messages as seen above.

It turns out the problem is (sort of) to do with comments that were migrated in to D7 from a D6 database.

It turns out the admins of the D6 site which we upgraded to D7 had deleted some users from the user table. In turn, this means there are comments in the comments table that have uids, but there is no corresponding user in the users table as it was deleted in the D6 system.

If you do manually import comments and are getting this error, check that you have got users that correspond to all comments. This is a good sql statement to use to check this:

SELECT * FROM `comment` WHERE uid NOT IN (SELECT uid FROM users)

If you get results, you can just update them to the anon user with this and it fixes the issue:

UPDATE `comment` SET uid = 0 WHERE uid NOT IN (SELECT uid FROM users)

I ran into this in Drupal seven too, but under different circumstances than the OP. I had created a theme for a new content-type that contained additional fields. Everything worked well until several weeks later I added some simple pages for privacy policies, etc.

The problem was that the preprocess_node function int the Template.php file manipulated fields that didn't exist in all content types. So it worked fine sometimes, but as soon as I did anything else it crashed.

The solution was to qualify the content-type for the fields I was manipulating.

For example:

function socialb_preprocess_node(&$variables) {
   // adjust fields if content_type is "polaroid"
   if (node_type_get_name($variables['node']) == "polaroid"){
     // do something to variables 
   }
}

#53
Posted by havard on April 28, 2011 at 2:08pm

Fixed this error for me. I had failed to set a filter to say that I only wanted a specific content type to load that view. When it tried to load other views (that I had created later), that did not have the image field, it broke the site as it could not find that field when trying to load the view.

Thanks.

FYI: I was running into this issue with media module installed and found out, after too much debugging, that an update of the media module (to 7.x-2.0-alpha3) added a media browser field to the file type "image". This broke my site in a lot of places. Deleting that field resolved the problem.