Problem/Motivation

The entity share client module provides an EntityImportStatus entity to track the various details of data entities that have been imported to your site. In its current implementation, It is possible to create a view of these EIS entities but it is not possible to join in the actual entity data tables to the view in order to display the field data of those imported entities. Likewise, it is possible to have views of data entities but there is no way to join in the EntityImportStatus data into those views (for example, if you wanted to do something like edit the default admin/content page to display which site the imported data entities came from).

Proposed resolution

  1. Override the views_data handler on the EntityImportStatus entity type to also support adding views relationships to join in the fields from all data entity tables.
  2. Implement hook_views_data_alter to add views relationships to each existing data entity type to allow joining in the related EntityImportStatus fields.
Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

Fernando Iglesias created an issue. See original summary.

fernando iglesias’s picture

StatusFileSize
new4.49 KB

Patch attached.

fernando iglesias’s picture

Status: Active » Needs review
grimreaper’s picture

Component: Entity share client » Code
Assigned: Unassigned » grimreaper

  • Grimreaper committed 94c597e2 on 8.x-3.x
    Issue #3341704 by Grimreaper, Fernando Iglesias: Improving the views...
grimreaper’s picture

Assigned: grimreaper » Unassigned
Status: Needs review » Fixed

Thanks.

I have tested creating a view on Entity import status and another view cloning the content admin list.

This now works in both directions.

It seems that when merging Gitlab is using the person who created the MR and not the first commit author. Sorry, you will get the credit being mentioned in the commit message and the issue.

Thanks again!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.