Project

General

Profile

Actions

Bug #23923

closed

FLUIDTEMPLATE (cObject) - Not parsing css id ?

Added by Sascha no-lastname-given about 14 years ago. Updated almost 14 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Communication
Target version:
-
Start date:
2010-11-02
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

I hope that i didn't miss any config or did something wrong.

The problem is that the frontend shows code like this:

<div id="c{field:uid}" class="csc-default" ><p class="bodytext"> </p>.....

It still shows typoscript code -> id="c{field:uid}"

My Typoscript:

page = PAGE
page.10 = FLUIDTEMPLATE
page.10 {

file = fileadmin/templates/mytemplate.html
partialRootPath = fileadmin/partials/
layoutRootPath = fileadmin/layouts/
variables {
mycontent = CONTENT
mycontent < styles.content.get
}
}

Template:

<p>{mycontent}<p>

(issue imported from #M16229)

Actions #1

Updated by Jo Hasenau about 14 years ago

I tried to reproduce this behaviour but the IDs are replaced correctly on our testing server.

But I get another bug, which is a weird looking output.
It seems that the HTML code gets processed by htmlSpecialChars so that you can read it in the frontend.

Can anyone confirm that?

Actions #2

Updated by Sascha no-lastname-given about 14 years ago

Hey Jo,

i think this is the normal Fluid behavior. Try this:

<f:format.html>{mycontent}</f:format.html>

The ViewHelper should solve this...

But i still see the CSS ID's. I tried it with just "Text" Elements. Every element gets wrapped with this div:
<div id="c{field:uid}" class="csc-default" >......</div

My Version is 4.5 alpha. Do you use the trunk ?

Actions #3

Updated by Jo Hasenau about 14 years ago

Of course I do :-)

I guess this bug can be closed, since the ID problem is related to the insertData Bug #23826, which is fixed in trunk.

Actions #4

Updated by Sascha no-lastname-given about 14 years ago

I tested the trunk version, everything fine now! No problem anymore.
Next time i only use the trunk for testing around.

Thanks alot.

Actions #5

Updated by Sascha no-lastname-given almost 14 years ago

i think this can be closed.

Actions #6

Updated by Chris topher almost 14 years ago

Thanks for the note!

Closed as requested.

Actions

Also available in: Atom PDF