[TYPO3-dev] RFC: a new page type "internal page" / "page container"

[Steffen Kamper]

"Steffen Kamper" <steffen at sk-typo3.de> schrieb im Newsbeitrag 
news:mailman.1.1194356073.30754.typo3-dev at lists.netfielders.de...
>
> "Steffen Kamper" <steffen at sk-typo3.de> schrieb im Newsbeitrag 
> news:mailman.1.1194308256.25394.typo3-dev at lists.netfielders.de...
>>
>
>>
>> To create a patch, i want ask what should happen with doktype 2 
>> (advanced). To be compatible it has to be there, but showing advanced 
>> page with same options than normal page looks bit strange. Any 
>> suggestions?
>>
>> vg  Steffen
>
> if there is no more suggestion i leave Advanced as it is and post the 
> patch in the afternoon in BT and core-list.
>
> vg  Steffen
>
>

ok, new features = new problems.

Tapio mentioned that container field is used in other doktypes too, e.g. 
mount pages.
So the question is now: Does it make sense to create the new doktype for the 
container-field if it's used in other doktypes as well?

Next problem Franz mentioned - if you switch doktype, the value of the field 
is leaved unchanged.
Example: filled containerfield will cause that these records are shown. if 
switched to "normal" you don't know why you don't see the infos you filled.
Same problem exists with doktype shortcut.

vg  Steffen