- 🇸🇪Sweden VAnnergard
Having had the same issue and stumbled on to this ticket, I think #6 is probably the reason this is a problem to start with.
The standard setting for rendered html output is to render it as an anonymous user which works as long as you have a public facing site but when you have limited access the output will (correctly) not fully render. Interesting some of the fields that are directly on the node did render, but not paragraphs that only worked when rendering as a user that had access to see the page.
Its an interesting question in this if it is a bug that the rendered html output when sat as an anonymous user still renders into the search index for pages where permission is denied for such users. (I guess as long as the search index is not publicly available its not a major issue)
- 🇦🇹Austria drunken monkey Vienna, Austria
Its an interesting question in this if it is a bug that the rendered html output when sat as an anonymous user still renders into the search index for pages where permission is denied for such users. (I guess as long as the search index is not publicly available its not a major issue)
For items that are not accessible to anonymous users, you should set up the search in a way (e.g., using the “Content access” processor) that doesn’t return the item to anonymous users (or others without access) anyways. So, I don’t think it’s a problem that the “Rendered HTML output” field doesn’t also account for this.