[TYPO3-dev] Nested CONTENT/select bug

[Armin Günther]

Hi Peter,

there has been a discussion of this "feature" here:

http://forge.typo3.org/issues/20541

The issue was closed as it could not be reproduced anymore. Now it looks 
as if you did reproduce it, so one might consider to reopen this "issue" 
(but as it is considered as a feature a feature request might be more 
appropriate).

In the discussion of this issue a solution was proposed by Jo Hasenau to 
make this recursion prevention mechanism optional by a switch like

removeDuplicatedRecords => boolean / default ON

But I don't know whether this switch was realized - I think it was not.

In my opinion this feature causes many hours of debugging for developers 
like you (and me some time ago) who are not aware of it. Is it 
documented in the TS Reference - I don' think so.

Best,
Armin




Am 27.07.2011 12:12, schrieb Peter Klein:
> Hi Jigal.
>
> Thanks for clearingit up for me.
> That explains why I got that "error".. :)
>
> --
> Peter Klein
>
> On Tue, 26 Jul 2011 18:58:37 +0200, Jigal van Hemert<jigal at xs4all.nl>
> wrote:
>
>> Hi,
>>
>> On 26-7-2011 18:14, Peter Klein wrote:
>>> I have a weird problem (Bug?)
>> No, it's a feature (really!).
>>
>>> The Typoscript below creates a "menu" of pages, sorted into sections
>>> based on the 1st letter of the page title.
>> [...]
>>> But instead of displaying all the results, it skips the 1st page in
>>> every section.??
>> CONTENT and RECORDS keep track of which records ("table:uid") are
>> already rendered. They won't render the same record twice to prevent
>> endless loops caused by recursion.
>>
>> In your case you use the same record twice for obviously different
>> purposes, but unfortunately this feature gets in the way. Although it's
>> not a very nice solution, you have found a clean workaround.
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev
>