Feature #19163

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

Added by Oliver Hader almost 5 years ago. Updated 11 days ago.

Status:On Hold Start date:2008-07-28
Priority:Should have Due date:
Assignee:Oliver Hader % Done:

0%
Category:-
Target version:-
TYPO3 Version:4.3 Complexity:
PHP Version:5.2
Votes: 0

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 (2.2 kB) Administrator Admin, 2008-07-28 15:42

History

#1
Updated by Andreas almost 5 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 5 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 5 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 5 years ago

Ok, now i've got it :)

#5
Updated by Alexander Opitz 12 days 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 11 days ago

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

#7
Updated by Oliver Hader 11 days ago

  • Status changed from Needs Feedback to On Hold

Also available in: Atom PDF