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.

Files: 
CommentFileSizeAuthor
#7 drupal-1882240-7.patch3.37 KBdawehner
PASSED: [[SimpleTest]]: [MySQL] 50,399 pass(es).
[ View ]
#6 drupal-1882240-6.patch2.68 KBdawehner
PASSED: [[SimpleTest]]: [MySQL] 50,753 pass(es).
[ View ]
render_controller_class.patch673 bytestim.plunkett
FAILED: [[SimpleTest]]: [MySQL] Failed to run tests: failed to login to test site.
[ View ]

Comments

Agreed, everything having this default is useless for us to work out which entities can be rendered and which can't! +1

Status:Needs review» Needs work

The last submitted patch, render_controller_class.patch, failed testing.

If we do something like that, we should certainly put something into entity_view_multiple to not fail totally, maybe throw an exception?

Status:Needs work» Needs review
Issue tags:-VDC

render_controller_class.patch queued for re-testing.

Status:Needs review» Needs work
Issue tags:+VDC

The last submitted patch, render_controller_class.patch, failed testing.

Status:Needs work» Needs review
StatusFileSize
new2.68 KB
PASSED: [[SimpleTest]]: [MySQL] 50,753 pass(es).
[ View ]

Let's see what happens if you add to all content entities.

StatusFileSize
new3.37 KB
PASSED: [[SimpleTest]]: [MySQL] 50,399 pass(es).
[ View ]

Added one for MenuLink and rerolled.

Status:Needs review» Reviewed & tested by the community

Thanks!

Status:Reviewed & tested by the community» Fixed

Make sense. Committed/pushed to 8.x.

Yay !

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

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