[Typo3] Upgrade to 3.8 causes RTE table html to be displayed as text

[Christopher]

Hi again,

On 01/07/05, Lyle E. Dodge <lyle.dodge at wwc.edu> wrote:
> Hi folks,
> 
> We finally fixed our problem here and are happy to report that all is well. :)
> 
> The problem was some TypoScript in the template setup field I had recently put in (first clue:
> check your recent changes, I should have learned this before).
> 
> On our site the <p>&nbsp;</p> stuff isn't so desirable so I removed it from
> ./typo3/sysext/css_styled_content/static/setup.txt.  That fixed work but isn't very future
> proof--as upgrades happen we'll have to go tweak that code each time.  So...I decided to put *a
> portion* (here's where I went wrong) of the items from the block I needed into my TypoScript.
> 
> lib.parseFunc_RTE < lib.parseFunc
> lib.parseFunc_RTE {
>           nonTypoTagStdWrap.encapsLines {
>                 encapsTagList = div,p,pre,h1,h2,h3,h4,h5,h6
>                 remapTag.DIV = P
>                 nonWrappedTag = P
>                 innerStdWrap_all.ifEmpty =             # removed &nbsp;
>                 #addAttributes.P.class = bodytext      # commented out
>                 #addAttributes.P.class.setOnly=blank   # commented out
>         }
> }
> 
> What I didn't realize in doing that (kicking myself now) was that by doing lib.parseFunc_RTE <
> lib.parseFunc I was overwriting that entire set of config values previously set by the
> css_styled_content setup.txt.  So...to resolve this problem I simply put _all_ of the
> lib.parseFunc_RTE setup TypoScript from setup.txt in there.
> 
> Seems a bit much just to remove the &nbsp; and class="bodytext" from P tags.  Is there an easier
> way or should I just keep all that code in my TypoScript?

If all you need to do is get rid of those two items, these two lines
in your main TS template ought to do it I think:

lib.parseFunc_RTE.nonTypoTagStdWrap.encapsLines.addAttributes >
lib.parseFunc_RTE.nonTypoTagStdWrap.encapsLines.innerStdWrap_all.ifEmpty = 

This is essentially what you'd done above, but without the copying
objects around; instead, you just unset (or set to an empty string)
the properties you don't want/need.

Incidentally, you're right: the configuration you describe _is_ a
little weird if you're using CSC; you said your template included:

lib.parseFunc_RTE < lib.parseFunc

...but (as I guess you've discovered), the static CSS Styled Content
template defines lib.parseFunc_RTE in the first place by copying
lib.parseFunc into it and then adding those other properties to it:

ib.parseFunc_RTE < lib.parseFunc
lib.parseFunc_RTE {
externalBlocks = table, blockquote, ol,ul
externalBlocks {
blockquote.stripNL=1
blockquote.callRecursive=1
...
...
...


In any case, I guess the point is that you can override _single_
properties in your template and just leave the rest of the default CSC
template alone until it causes problems :^)


-Christopher