If displaying a rendered entity in a view, role must have edit permissions to avoid fatal memory exhaustion.

I’m guessing this is based around how the display page gets routed to /edit/, so even in a view render it gets stuck in a loop going from render to edit to render or something.

I

I

I

I was able to work around this by using https://www.drupal.org/project/field_permissions → to just make so the role I wanted to be able to see this entity type can't edit any of the fields. A little annoying, and it means being careful when adding new fields as they can hit them by manually figuring out where to go URL wise but it worked.

Interestingly this seems to be possibly related to https://www.drupal.org/project/storage/issues/3460699 🐛 Contents of file fields in storage entities not viewable without permissions for "View published Storage entities" Active - I only had to do this for two entity types that had file fields on them. An entity type that I wanted to render as a field in a view without a file field works without any permissions change. I didn't notice this before as all 3 views for a single entity used each other's related entities in a different format with their own views tucked in on the bottom via VFV.

The comment form glitched out - I reported the previous ones as spam and hopefully they'll get removed.