Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
It would be nice to differentiate between an entity type that can be rendered, and one that shouldn't.
If any class is actually using EntityRenderController, it should do that explicitly.
Comment | File | Size | Author |
---|---|---|---|
#7 | drupal-1882240-7.patch | 3.37 KB | dawehner |
#6 | drupal-1882240-6.patch | 2.68 KB | dawehner |
render_controller_class.patch | 673 bytes | tim.plunkett | |
Comments
Comment #1
damiankloip CreditAttribution: damiankloip commentedAgreed, everything having this default is useless for us to work out which entities can be rendered and which can't! +1
Comment #3
dawehnerIf we do something like that, we should certainly put something into entity_view_multiple to not fail totally, maybe throw an exception?
Comment #4
damiankloip CreditAttribution: damiankloip commentedrender_controller_class.patch queued for re-testing.
Comment #6
dawehnerLet's see what happens if you add to all content entities.
Comment #7
dawehnerAdded one for MenuLink and rerolled.
Comment #8
tim.plunkettThanks!
Comment #9
catchMake sense. Committed/pushed to 8.x.
Comment #10
yched CreditAttribution: yched commentedYay !
Now rdf.module can stop running db queries whenever the definition of a (view|image style|input format|layout breakpoint...) is loaded :-p #1920498: Have rdf.module only act on renderable entities