TYPO3 Core

Frans,
cheers for looking into this.

Well, the current active standard is like this (landing page ts):

TCAdefaults.pages.url_scheme = 2
TCEFORM.pages.layout {
addItems {
4 = Landing page design
}
altLabels {
0 = Article-setup
1 = News Setup
2 = VACC countries
3 = Special pages
}
}

So, nothing special i think. The different layouts of course are covered by the template to setup the looks.

I have tried those sets:

lib.parseFunc_RTE {
externalBlocks {
ol {
stripNL = 1
stdWrap.parseFunc = < lib.parseFunc
}
ul {
stripNL = 1
stdWrap.parseFunc = < lib.parseFunc
}
}
}

lib.parseFunc_RTE {
externalBlocks := addToList(ul)
externalBlocks {
ul.stripNL = 1
ul.callRecursive = 1
ul.callRecursive.tagStdWrap.HTMLparser = 1
ul.callRecursive.tagStdWrap.HTMLparser.tags.ul {
fixAttrib.class.default = contentList
}
}
}

And they didn't have impact on the problem. Unfortunately. BTW. here is a link to the page i am currently building: http://prod.vateud.net/index.php?id=11

Snapshot is amended.

And again: thanks for helping to identify it.

Florian

Florian Harms wrote:

Frans Saris wrote:

Are you using a clean/fresh install or are there any special extensions etc?

Can you show us your pageTS especially RTE.proc.
Maybe create a screenshot of the BE info module.

And can you check what is saved in the database.

Looks like you have some old (pre TYPO3 8.7) RTE.proc that is the cause of this issue.

And yes, this is a clean install on a new box... installed last Tuesday. Looking for the RTE.proc

Good afternoon again...

Mission accomplished. It was a typoscript thingy i have created myself. So, no worries to the setup.

I was simply checking a bit and found out that the OL tag was not creating the additional <P>. Therefore I have created a very basic ts template and the UL, LI part was working absolutely correct. The error was self made in the RTE configuration typoscript to add a few more switches for the editors fun. And one added the extra line.

As we all know: "Ignorance is the mother of all adventures"... :)

Thanks again for your great work.

Florian

Good to hear the issue is resolved