Project

General

Profile

Actions

Bug #37988

closed

COA_INT in Fluid-Templates

Added by Alexander Wende almost 12 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
Start date:
2012-06-13
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
9
PHP Version:
5.5
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
Stabilization Sprint

Description

I think this is a related bug to http://forge.typo3.org/issues/36820
Passing a coa_int object to a fluidtemplate cause
an <!--INT_SCRIPT output like wrapping a coa_int in another coa_int.
atm the fluid template has no partials...

Can anybody confirm?

  10 = FLUIDTEMPLATE
  10 {
      file = {$filepaths.templatePath}{$filepaths.templatefile}
      partialRootPath = {$filepaths.partialPath}    
      layoutRootPath = {$filepaths.layoutPath}   
      variables{
         username = COA_INT
         username.10 = TEXT
         username.10.value = some username
      }
   }

Typo3 4.6.9


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #44825: Pagerenderer / page.headerData + USER_INT is not workingClosedHelmut Hummel2013-01-26

Actions
Actions #1

Updated by Christian Kuhn about 11 years ago

  • Status changed from New to Needs Feedback

@Alexander: We've have a nifty patch in this area for TYPO3 CMS 6.0. Is this still reproducible for you with this core version?

Actions #2

Updated by Alexander Opitz over 10 years ago

No feedback for over 90 days.

Actions #3

Updated by Alexander Opitz over 10 years ago

  • Status changed from Needs Feedback to Closed
Actions #4

Updated by Christian Eßl over 10 years ago

I can confirm this in TYPO3 6.1.3 when using the cObject viewhelper.

lib.test = COA_INT
lib.test {
10 = TEXT
10.value = test
}

{f:cObject(typoscriptObjectPath: 'lib.test')}

leads to output like this:

@@

Actions #5

Updated by Sander Leeuwesteijn over 10 years ago

This is also happening in 6.1.5!

Actions #6

Updated by Manuel Thaler about 10 years ago

Sander Leeuwesteijn wrote:

This is also happening in 6.1.5!

Still seems to be a problem. Any idea how to solve it?
This here didn't solve it either:
http://forge.typo3.org/issues/37988

Maybe you have a look at this:
http://www.typo3.net/forum/thematik/zeige/thema/90982/?show=1

Actions #7

Updated by Xavier Perseguers almost 9 years ago

  • Status changed from Closed to Accepted
  • Target version set to 6.2.14
  • Is Regression set to No
  • Sprint Focus set to Stabilization Sprint

Can reproduce the problem. Should get fixed finally :)

Actions #8

Updated by Helmut Hummel almost 9 years ago

  • Status changed from Accepted to Needs Feedback

Christian Eßl wrote:

I can confirm this in TYPO3 6.1.3 when using the cObject viewhelper.

lib.test = COA_INT
lib.test {
10 = TEXT
10.value = test
}

{f:cObject(typoscriptObjectPath: 'lib.test')}

I cannot confirm this. Using the cObject view helper works like expected

Actions #9

Updated by Helmut Hummel almost 9 years ago

It is important to not htmlencode the output of a COA_INT or USER_INT

The following code could be used in case the COA_INT is used as Fluid variable in TS

<f:format.raw>{username}</f:format.raw>

With that, everything works like expected.

Actions #10

Updated by Xavier Perseguers almost 9 years ago

  • Status changed from Needs Feedback to Resolved
  • % Done changed from 0 to 100

Thanks for the hint.

Actions #11

Updated by Riccardo De Contardi over 6 years ago

  • Status changed from Resolved to Closed
Actions #12

Updated by Vasyl Mosiychuk over 4 years ago

  • TYPO3 Version changed from 4.6 to 9
  • PHP Version changed from 5.3 to 5.5

This issue not resolved for me...

in TS


lib.currentUidUserInt = COA_INT
lib.currentUidUserInt {
    10 = TEXT
    10.data = TSFE:fe_user|user|uid
}

In FLUID


{f:cObject(typoscriptObjectPath:'lib.currentUidUserInt') -> v:variable.set(name:'foo')}

here I get `UID` and it is works


{foo -> f:format.raw()}

But here I get problem


<f:if condition="{0:'{newsFeUser.0.uid}'} == {0:'{foo -> f:format.raw()}'}">

I get...


<!--INT_SCRIPT.747d1dced8da2c172a57e825026c429b-->

Actions #13

Updated by Patrick Crausaz about 4 years ago

  • % Done changed from 100 to 0

This is not resolved! The problem still exists in version 9.5.14

Actions #14

Updated by Bernhard Berger over 3 years ago

I also get INT_SCRIPT tags when I try to render content (RECORDS) via PageRenderer->addJsInline()..

TYPO3 9.5.19

This leads to stuff like:

"data":"{"foo":"bar"} after eventually being replaced (notice the quote after the colon as ot gets rendered as "<!-- INT_SCRIPT.." string first and then replaced while still being within quotes......

Actions #15

Updated by Jonas Eberle about 3 years ago

There were reports about v9.

I cannot reproduce in v9, v10 and current master with this snippet:

lib.coaInt = COA_INT
lib.coaInt {
  10 = TEXT
  10.data = date:U  
}

page.1234 = FLUIDTEMPLATE
page.1234 {
  template = TEXT
  template.value (
    coaInt: <f:cObject typoscriptObjectPath="lib.coaInt" />
  )
}
Actions #16

Updated by Julian Hofmann about 3 years ago

It seems to depend on when Fluid allows the COA_INT-cObject to be rendered, i.e. when it still exists as "" and when the timestamp is in it.

Snippet:

page.1234 = FLUIDTEMPLATE
page.1234 {
  variables {
    timestamp = TEXT
    timestamp.data = date:U  
  }
  template = COA
  template {
    5 = TEXT
    5.value (
      timestamp: {timestamp}<br />
    )
    10 = TEXT
    10.value (
      coaInt: <f:cObject typoscriptObjectPath="lib.coaInt" /><br />
    )
    15 = TEXT
    15.value (
      "{f:cObject(typoscriptObjectPath:'lib.coaInt')}=={timestamp}" is
      <f:if condition="{f:cObject(typoscriptObjectPath:'lib.coaInt')}=={timestamp}"><f:then>true</f:then><f:else><strong>false</strong></f:else></f:if>
    )
}

Result:

timestamp: 1614173785
coaInt: 1614173785
"1614173785==1614173785" is false

(Tested with TYPO3 v10.4.13)

Actions #17

Updated by Christian Kuhn over 1 year ago

Hey.

Discussing on an issue that has been closed long ago does not raise much awareness to others.

If the issue still exists one way or the other, could you please open a fresh issue, maybe re-describing the issue and link to this issue as well?

Actions #18

Updated by Philipp Kitzberger about 1 year ago

Had the same issue with TYPO3 10.4 and used this to prevent Fluid from destroying the INT_SCRIPT marker:

{username -> f:format.raw()}

Kudos to TYPO3 legend @Ernesto Baschny!

Actions

Also available in: Atom PDF