Feature #19163

Automatically execute nested USER_INT/COA_INT objects as regular USER/COA objects

Added by Oliver Hader almost 11 years ago. Updated over 1 year ago.

Status:
Needs Feedback
Priority:
Should have
Assignee:
Category:
TypoScript
Start date:
2008-07-28
Due date:
% Done:

0%

PHP Version:
5.2
Tags:
Complexity:
Sprint Focus:

Description

Imagine you have the following situation in TypoScript:
10 = COA_INT
10 {
10 = COA_INT
10 {
10 = COA_INT
10 {
10 = TEXT
10.value = Test
}
}
}
The nestification of the COA_INT objects would result in recursing calls for each new level of that *_INT object. However, for the first occurence of COA_INT the caching for that object and nested objects is already disabled - thus it's not required to perform this task again.

(issue imported from #M9065)

0009065.patch View (2.17 KB) Administrator Admin, 2008-07-28 15:42

History

#1 Updated by Andreas almost 11 years ago

this is bad typoscript programming. nobody should programming like this.

correct way:

10 = COA_INT
10 {
10 = COA
10 {
10 = COA
10 {
10 = TEXT
10.value = Test
}
}
}

#2 Updated by Oliver Hader almost 11 years ago

Ooooh yeah! Absolutely right, it should not. But it defintively happens! So, any more constructive feedback?!
And by the way... the attached patch is exactly doing what you did manually...

#3 Updated by Oliver Hader almost 11 years ago

To justify this issue, imagine you get an extension from TER that sets up the following TypoScript:
plugin.tx_myext_pi1 = USER_INT
plugin.tx_myext_pi1 {
...
}

And then you'd just put it somewhere to your page, inside a COA_INT like this:
page = PAGE
page.10 = COA_INT
page.10.10 =< plugin.tx_myext_pi1

Here we go... and there are more variants how this easily could happen...

#4 Updated by Andreas almost 11 years ago

Ok, now i've got it :)

#5 Updated by Alexander Opitz about 6 years ago

  • Category deleted (Communication)
  • Status changed from Accepted to Needs Feedback
  • Target version deleted (0)

As this report is very old, is the handling in newer TYPO3 CMS Versions (like 6.0/6.1) more like you expect it?

#6 Updated by Oliver Hader about 6 years ago

The handling is still the same in TYPO3 CMS 6.x.

#7 Updated by Oliver Hader about 6 years ago

  • Status changed from Needs Feedback to On Hold

#8 Updated by Mathias Schreiber over 4 years ago

  • Target version set to 7.2 (Frontend)

#9 Updated by Benni Mack about 4 years ago

  • Target version changed from 7.2 (Frontend) to 7.4 (Backend)

#10 Updated by Susanne Moog almost 4 years ago

  • Target version changed from 7.4 (Backend) to 7.5

#11 Updated by Benni Mack almost 4 years ago

  • Target version changed from 7.5 to 8 LTS

#12 Updated by Riccardo De Contardi over 2 years ago

  • Target version changed from 8 LTS to 9.0

#13 Updated by Benni Mack over 1 year ago

  • Status changed from On Hold to Needs Feedback

So how about pushing your idea to gerrit and add tests to that?

#14 Updated by Susanne Moog over 1 year ago

  • Category set to TypoScript

#15 Updated by Susanne Moog over 1 year ago

  • Target version changed from 9.0 to Candidate for Major Version

Also available in: Atom PDF