Feature #19163
open
Automatically execute nested USER_INT/COA_INT objects as regular USER/COA objects
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)
Files
Updated by Andreas over 15 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
}
}
}
Updated by Oliver Hader over 15 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...
Updated by Oliver Hader over 15 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...
Updated by Alexander Opitz almost 11 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?
Updated by Oliver Hader almost 11 years ago
The handling is still the same in TYPO3 CMS 6.x.
Updated by Oliver Hader almost 11 years ago
- Status changed from Needs Feedback to On Hold
Updated by Mathias Schreiber over 9 years ago
- Target version set to 7.2 (Frontend)
Updated by Benni Mack almost 9 years ago
- Target version changed from 7.2 (Frontend) to 7.4 (Backend)
Updated by Susanne Moog over 8 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack over 8 years ago
- Target version changed from 7.5 to 8 LTS
Updated by Riccardo De Contardi about 7 years ago
- Target version changed from 8 LTS to 9.0
Updated by Benni Mack over 6 years ago
- Status changed from On Hold to Needs Feedback
So how about pushing your idea to gerrit and add tests to that?
Updated by Susanne Moog about 6 years ago
- Target version changed from 9.0 to Candidate for Major Version
Updated by Benni Mack almost 4 years ago
- 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.
Updated by Benni Mack almost 4 years ago
- Status changed from Rejected to Accepted
Updated by Gerrit Code Review about 1 year ago
- Status changed from Accepted to Under Review
Patch set 1 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77841
Updated by Gerrit Code Review about 1 year ago
Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77841