Feature #19163
open
Automatically execute nested USER_INT/COA_INT objects as regular USER/COA objects
Added by Oliver Hader over 15 years ago.
Updated about 1 year ago.
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)
Files
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
}
}
}
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...
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...
- 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?
The handling is still the same in TYPO3 CMS 6.x.
- Status changed from Needs Feedback to On Hold
- Target version set to 7.2 (Frontend)
- Target version changed from 7.2 (Frontend) to 7.4 (Backend)
- Target version changed from 7.4 (Backend) to 7.5
- Target version changed from 7.5 to 8 LTS
- Target version changed from 8 LTS to 9.0
- Status changed from On Hold to Needs Feedback
So how about pushing your idea to gerrit and add tests to that?
- Category set to TypoScript
- Target version changed from 9.0 to Candidate for Major Version
- Status changed from Needs Feedback to Rejected
Won't do. This is a nice to have one, but definitively makes the complexity higher. Instead, let's treat each USER/COA as a cached response and use that one instead.
- Status changed from Rejected to Accepted
- Status changed from Accepted to Under Review
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by