Problem/Motivation

After I ran a D7->D8 migration my destination site is now broken. Everytime I click on admin/content I get an error

Fatal error: Call to a member function getEntityTypeId() on null in drupal8\core\modules\views\src\Plugin\views\field\EntityOperations.php on line 102

It destryed my destination site and I cannot recover.

Proposed resolution

Remaining tasks

User interface changes

None

API changes

None

Data model changes

None

Comments

hass created an issue. See original summary.

kylebrowning’s picture

kylebrowning CreditAttribution: kylebrowning commented

You should always backup the database before an update.

What modules did you have installed?

hass’s picture

hass CreditAttribution: hass commented

On the D8? Just core, google analytics and the required migrate modules with migrate_upgrade.

How can I debug it to the root cause?

kylebrowning’s picture

kylebrowning CreditAttribution: kylebrowning commented

On your D7 Site.

hass’s picture

hass CreditAttribution: hass commented

block
advanced_help
blog
book
ckeditor
colorbox
contact
contextual
ctools
diff
elements
entitycache
field
field_sql_storage
field_ui
file
filefield_paths
filter
fivestar
geshifilter
googleanalytics
help
html5_tools
image
imce
l10n_update
libraries
linkchecker
list
locale
menu
navbar
node
number
options
path
pathologic
php
piwik
profile
robotstxt
search
speedy
system
taxonomy
text
translation
transliteration
update
update_advanced
user
views_ui
votingapi
xmlsitemap_taxonomy
ckeditor_link
pathauto
xmlsitemap
xmlsitemap_engines
xmlsitemap_node
token
views
insert
dblog
redirect
statistics
devel

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
CreditAttribution: phenaproxima at Acquia commented
Issue tags: -Migrate D7 critical

This should not be Migrate D7 critical until we have more information on what caused it, how to reproduce it, and what the fix is.

hass’s picture

hass CreditAttribution: hass commented

How may I found out what is causing this issue? Any hints?

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
CreditAttribution: phenaproxima at Acquia commented

I would recommend using Xdebug to set a breakpoint at the line which is triggering the fatal error and trace back from there. My guess is that there's something wrong with some entity, so finding out what entity it is, and if it has any invalid data, would be a good first step.

quietone’s picture

quietone CreditAttribution: quietone as a volunteer commented
Version: 8.0.0-beta15 » 8.1.x-dev

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan as a volunteer and at Virtuoso Performance commented
Status: Active » Postponed (maintainer needs more info)

Can anyone reproduce this error these days?

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan as a volunteer and at Virtuoso Performance commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

No further information provided.

cristian100’s picture

cristian100
Primary language Spanish
Location Tepic Nayarit
CreditAttribution: cristian100 as a volunteer commented

I have this bug using entity_browser, once I upload a file that is set to be saved into my library, when I want in another node to select an existing image, I get this message:

Call to a member function getEntityTypeId() on null in /var/www/html/modules/contrib/entity_browser/src/Plugin/views/field/SelectForm.php on line 28

cristian100’s picture

cristian100
Primary language Spanish
Location Tepic Nayarit
CreditAttribution: cristian100 as a volunteer commented
Status: Closed (cannot reproduce) » Active
mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan as a volunteer and at Virtuoso Performance commented
Status: Active » Postponed (maintainer needs more info)

@cristian100: Does what you're seeing have anything to do with migration? You don't mention migration in your description.

Note that your error message is reported in the contrib entity_browser module, not in the core views module as the original problem report here was. If your problem is unrelated to the core migration system, you should open a bug report in the entity_browser issue queue.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan as a volunteer and at Virtuoso Performance commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

No reproducible instance of this error involving migration.