TYPO3 Core

Hey,
try to change the rendering from <format.html> to <format.raw> in fluid styled content. That should do the trick.

I don't think so, because i don't use a variable:

lib.content = CONTENT
lib.content {
  table = tt_content
  select {
    orderBy = sorting
    where.field = colPos
    where.intval = 1
    where.wrap = colPos=|
    languageField = sys_language_uid
  }
}

<f:cObject typoscriptObjectPath="lib.content"/>

This also happens with a simple

page.10 < styles.content.get

OK, I should read you whole answer before I reply.

Changing every fluid_styled_content template just because of rte_ckeditor is, well, ...
I go with rtehtmlarea for now.

How would you implement a core patch? A snd template root path for fluid_styled_content if rte_ckeditor is loaded?

But I think, format.raw is not a good solution at all!

https://forge.typo3.org/issues/71878#note-13 could be a solution?

yes, that's only one restriction of the ckeditor configuration delivered with v8.5. basically, no content transformation was ever applied. this is partially fixed in master already, and benni is currently working on a better configuration system of the editor.

Why is this issue closed? #79351 is closed as related to this one. And this seems to be closed because #79351 is resolved?

Anyway, I still have this problem and have not found any leverage to get rid of the continuously growing number of empty paragraphs on every save.

I am using a custom content element with this fairly straight forward configuration:

    <f:section name="Configuration">
        <flux:form id="tabs"  options="{group: 'my-elements'}">
            <flux:form.section name="tabs" label="Tab">
                <flux:form.object name="tab">
                    <flux:field.input name="title" label="title"/>
                    <flux:field.text name="content" label="text" enableRichText="true"/>
                </flux:form.object>
            </flux:form.section>
        </flux:form>
    </f:section>

Guys, this works for me very well

<f:format.html parseFuncTSPath="">

The only downside is that you have to change it in the FSC files.
And the question, is this solution safe ?

the solutions are no sulutions - the problem starts in BE when you edit a text with paragraphs. For me, after each save, empty paragraphs are added between each existing paragraph.
So the problem must be solved at this place, and not supressing this error in FE rendering!

OK - i tried with different types of text, and the problem is inside flux

Using defaultExtras in text configuration leads to the problem. Solution is not to use defaultExtras, but enableRichtext = true instead.

So i will do a change request for FLUX , and for core the issue does not exist (as long as you do not change the TCA for mode)

For me the ticket can be closed.

Stephen Kamper thx i also added hard coded as you told. Approximately in 60 line in
typo3conf/ext/flux/Classes/Form/Field/Text.php

if (true === $this->getEnableRichText() && true === empty($defaultExtras)) {
    $typoScript = $this->getConfigurationService()->getAllTypoScript();
    $configuration['enableRichtext'] = true;
} else {
    $configuration['defaultExtras'] = $defaultExtras;
}