From entity_views_data():

  // Add tables based upon data selection "queries" for all entity types.
  foreach (entity_get_info() as $type => $info) {
    $table = entity_views_table_definition($type);
    if ($table) {
      $data['entity_' . $type] = $table;
    }
    // Generally expose properties marked as 'entity views field'.
    $data['views_entity_' . $type] = array();
    foreach (entity_get_all_property_info($type) as $key => $property) {
      if (!empty($property['entity views field'])) {
        entity_views_field_definition($key, $property, $data['views_entity_' . $type]);
      }
    }
  }

I don't see why this should clobber existing data that the views controller class could be exposing for 'views_entity_' . $type. This makes it impossible to add pseudo fields in the style of node edit and delete links that build upon views_field_handler_entity.

CommentFileSizeAuthor
#1 2192483-entity_views_data-1.patch686 bytesmikey_p
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mikey_p’s picture

Status: Active » Needs review
FileSize
686 bytes

This should be sufficient.

Chris Matthews’s picture

Version: 7.x-1.3 » 7.x-1.x-dev

The 5 year old patch to entity.views.inc applied cleanly to the latest entity 7.x-1.x-dev and (if still relevant) needs review.