The "" entity type does not exist. in Drupal\Core\Entity\EntityTypeManager->getDefinition() ( [#2875000]

After upgrading to => drupal 8.3.1, Panels 8.x-4.1 , Page Manager 8.x-4.0-beta2 and Panelizer 8.x-4.0
Im not able to use the panelizer ipe anymore , cant change layout and/or add/remove content from my panelized content types.
I keep getting the following error

Location : http://mysite.dev/admin/panels_ipe/variant/panelizer_default/*node:226:full:default/layouts/layout_twocol_bricks
Message : Drupal\Component\Plugin\Exception\PluginNotFoundException: The "" entity type does not exist. in Drupal\Core\Entity\EntityTypeManager->getDefinition() (line 133 of 
Sites/mysite/core/lib/Drupal/Core/Entity/EntityTypeManager.php).

I have checked this issue , but seems to be another bug that didnt help in my case.

Any help would be appreciated :)

Comments

Comment #1

2 May 2017 at 19:36

Orabi created an issue. See original summary.

Comment #2

Orabi CreditAttribution: Orabi as a volunteer commented 2 May 2017 at 19:37

Comment #3

weldonpatterson CreditAttribution: weldonpatterson commented 8 May 2017 at 20:32

I'm experiencing the same issue

Comment #4

addiction2code CreditAttribution: addiction2code commented 12 June 2017 at 23:45

This same issue is also effecting my project, using the same versions as Orabi except Drupal Core (8.3.3).

Comment #5

BR0kEN

Ukrainian

CreditAttribution: BR0kEN as a volunteer and at FFW, Drupal Ukraine Community for Propeople (now part of FFW), FFW commented 13 June 2017 at 08:09

It could be that you are experiencing this from Panelizer.

Comment #6

GAMe CreditAttribution: GAMe commented 2 August 2017 at 14:01

Im having the same issue when trying to install these modules on a fresh D8.3 install, however, I turned on layout_discovery before enabling panels. Could this be the issue? I will try to run some more tests but currently, panels is unusable.

ok so im not using panelizer just page manager and still getting this issue. I have created this same issue for page manager as my gut is saying its an issue with this. Looking at the error, and I know this sounds like a silly comment but when page manager installs is it meant to create an entity called "page" which isnt being created.

https://www.drupal.org/node/2899323

Comment #7

GAMe CreditAttribution: GAMe commented 2 August 2017 at 14:01

Priority:

Normal

» Critical

Comment #8

GAMe CreditAttribution: GAMe commented 3 August 2017 at 08:48

This morning I saw an update to core 8.3.6 so I have run the update and updated all other modules from dev to stable (As they were before I started testing) and now all is fine so possibly an issue with core.

Comment #9

alexmoreno CreditAttribution: alexmoreno commented 29 August 2017 at 10:07

using 8.3.7, issue is still there

Comment #10

Orabi CreditAttribution: Orabi as a volunteer commented 29 August 2017 at 19:32

Sorry for coming back very late.
But I just checked again and I think that this problem has something to do with the default value of panelizer display : here is what i found/did

So first : I have
drupal 8.3.4, Panels 8.x-4.1 , panels IPE 8.x-4.1,panelizer_quickedit: 8.x-4.0 Page Manager 8.x-4.0-beta2 and Panelizer 8.x-4.0

Go to your content type
manage display
Check those 3 checkboxes
1-Panelize this view mode
2-Allow each content item to have its display customized
3-Allow users to select which display to use
SAVE
click on Add a new Panelizer default display
next next ( you know what to do ) and save.
GO TO : Manage form display
Let the paneizer field show up on the node edit form
save
go to your node and choose your NEW display ( which is not the default )
save and publish your node
for me was it => voila :)

So this is just to have it working for now. but needs more work to find the real problem
ps: Im also not sure if you HAVE to check the 3 checkboxes from panelizer , but thats what i have now and ill test the other cases later on.

Plz let know if this worked out for your cases.

** if you go back to your node and you choose the default display back , then the problem comes back again :(

Would be also useful if you can try this with a new CT, try to make one display and see if it works! if not=> make another display and check with the new display.

Comment #11

dimr CreditAttribution: dimr commented 25 September 2017 at 10:12

Issue tags:

+Drupalcon Vienna 2017

I have tried #10 and it works to me, Drupal 8.3.7 and Panelizer 8.x-4.0
Thanks!

Comment #12

dahdoul CreditAttribution: dahdoul commented 27 September 2017 at 20:17

#10 worked for me thanks

Comment #13

DamienMcKenna

NH, USA

CreditAttribution: DamienMcKenna at Mediacurrent commented 28 September 2017 at 02:47

Version:

8.x-4.1

» 8.x-4.x-dev

Comment #14

drumm

he/him

NY, US

CreditAttribution: drumm at Drupal Association commented 28 September 2017 at 15:37

Issue tags:

-Drupalcon Vienna 2017

+Vienna2017

Updating to the canonical tag for DrupalCon Vienna 2017.

Comment #15

todda CreditAttribution: todda commented 13 November 2017 at 15:04

#10 works great. Thank You!!!

Comment #16

glass.dimly CreditAttribution: glass.dimly commented 21 March 2018 at 13:48

The other workaround here (if you don't need per-node or per-user panelerized nodes) is to forgo the in-place editor and edit from "Structure" -> "Content type" -> "Manage display" -> "Edit".

This is still a critical bug, even though a workaround appears to exist.

Comment #17

alphex CreditAttribution: alphex commented 18 April 2018 at 21:10

Drupal 8.5.1

Panelizer 8.4.1 with all required dependencies.

Comment #10 works to solve the problem.

Thoughts -
I would think that if you AREN'T allowed to customize the page, you shouldn't be given that button on the IPE...

And burying the error in a silent 500 error that I only saw in DEV tools could probably stand to get a nice error message on the front end for the normal site builder if this is "working as designed"

Comment #18

malmeida287 CreditAttribution: malmeida287 commented 25 July 2018 at 09:51

Checking

2-Allow each content item to have its display customized

Solved my problem.

Thanks Orabi - #10 !

Btw, I agree with #16 and #17, this is still a bug though: if we're not allowed to save due to configurations, we should be warned about it instead of getting this error 500.

Comment #19

edorsini CreditAttribution: edorsini commented 12 March 2019 at 20:04

I just updated to Drupal 8.6.10 and I am getting the following error in the logs when I visit /admin/modules (I get a WSOD):

Drupal\Component\Plugin\Exception\PluginNotFoundException: The "" entity type does not exist. in Drupal\Core\Entity\EntityTypeManager->getDefinition() (line 133 of

I am using the Lightning Distribution currently at 3.2.6. Any one else having the same issues?

Comment #20

sisko CreditAttribution: sisko commented 18 October 2019 at 07:33

Same issue:

The website encountered an unexpected error. Please try again later.</br></br><em class="placeholder">Drupal\Component\Plugin\Exception\PluginNotFoundException</em>: The &quot;page_variant&quot; entity type does not exist. in <em class="placeholder">Drupal\Core\Entity\EntityTypeManager-&gt;getDefinition()</em> (line <em class="placeholder">150</em> of <em class="placeholder">core/lib/Drupal/Core/Entity/EntityTypeManager.php</em>). <pre class="backtrace">Drupal\Core\Entity\EntityTypeManager-&gt;getHandler(&#039;page_variant&#039;, &#039;storage&#039;) (Line: 208)
Drupal\Core\Entity\EntityTypeManager-&gt;getStorage(&#039;page_variant&#039;) (Line: 187)
Drupal\Core\Entity\EntityRepository-&gt;getCanonicalMultiple(&#039;page_variant&#039;, Array, Array) (Line: 180)
Drupal\Core\Entity\EntityRepository-&gt;getCanonical(&#039;page_variant&#039;, &#039;homepage-panels_variant-0&#039;, Array) (Line: 149)
Drupal\Core\ParamConverter\EntityConverter-&gt;convert(&#039;homepage-panels_variant-0&#039;, Array, &#039;page_manager_page_variant&#039;, Array) (Line: 100)
Drupal\Core\ParamConverter\ParamConverterManager-&gt;convert(Array) (Line: 45)
Drupal\Core\Routing\Enhancer\ParamConversionEnhancer-&gt;enhance(Array, Object) (Line: 260)
Drupal\Core\Routing\Router-&gt;applyRouteEnhancers(Array, Object) (Line: 131)
Drupal\Core\Routing\Router-&gt;matchRequest(Object) (Line: 92)
Drupal\Core\Routing\AccessAwareRouter-&gt;matchRequest(Object) (Line: 113)
Symfony\Component\HttpKernel\EventListener\RouterListener-&gt;onKernelRequest(Object, &#039;kernel.request&#039;, Object)
call_user_func(Array, Object, &#039;kernel.request&#039;, Object) (Line: 111)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher-&gt;dispatch(&#039;kernel.request&#039;, Object) (Line: 127)
Symfony\Component\HttpKernel\HttpKernel-&gt;handleRaw(Object, 1) (Line: 68)
Symfony\Component\HttpKernel\HttpKernel-&gt;handle(Object, 1, 1) (Line: 57)
Drupal\Core\StackMiddleware\Session-&gt;handle(Object, 1, 1) (Line: 47)
Drupal\Core\StackMiddleware\KernelPreHandle-&gt;handle(Object, 1, 1) (Line: 191)
Drupal\page_cache\StackMiddleware\PageCache-&gt;fetch(Object, 1, 1) (Line: 128)
Drupal\page_cache\StackMiddleware\PageCache-&gt;lookup(Object, 1, 1) (Line: 82)
Drupal\page_cache\StackMiddleware\PageCache-&gt;handle(Object, 1, 1) (Line: 47)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware-&gt;handle(Object, 1, 1) (Line: 52)
Drupal\Core\StackMiddleware\NegotiationMiddleware-&gt;handle(Object, 1, 1) (Line: 23)
Stack\StackedHttpKernel-&gt;handle(Object, 1, 1) (Line: 693)
Drupal\Core\DrupalKernel-&gt;handle(Object) (Line: 19)
</pre>