Sébastien Ros

Personally I think it's fine to have it in the Default tenant. If it had to be doable from another tenant then we'd have to change what "Default" tenant means....

I don't think it's a solution to change the current behavior. I would prefer a new API that works on content item version ids, so you can delete a specific...

Ok with breaking changes but then only if we complete the API such that it's consistent and there is a way to do what was done before.

Maybe it's a bug, but the mitigation is to just not create the input for the ListPart. I don't see it as something that really needs to be checked for...

To be able to customize a page without the need of create a custom template for the type if you only need some custom css.

Does it solve the problem? Also this is for Html field only, the same issue should appear with TextField, HtmlBodyPart and MarkdownBody

> I was unable to repro the initial error after reverting the change If you tested on a content that was already indexed with the fix then it would explain....

Or maybe someone can manually reproduce the issue and then confirm the PR is fixing it.

It means that when the "analyzed" option is checked there is no issue even with huge documents? Then should we only split the documents in these cases?

I'd like you to confirm something. The issue only happens when "Stored" is selected. The intent of this property is to be able to read the original value that was...