Trying to access invalid (or not installed) entity views should produce an HTTP 404 error, not a HTTP 500 error - the current behavior makes it look like something went wrong on the server, when actually it is just an invalid request from the client.
I poked around a bit in the `LogTypeManager`/`AssetTypeManager`, but didn't obviously see what needs to change to produce the correct behavior here.
N/A
This should return the generic "Page not found" 404 error.
N/A
N/A
Needs work
3.0
User interface
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.