[TYPO3-core] RFC: #6703 $TCA[table]['ctrl']['hideTable'] not implemented

[Oliver Hader]

Hi Ingmar,

Ingmar Schlecht schrieb:
> Malte Jansen schrieb:
>> Dmitry Dulepov [typo3] schrieb:
>>> Ingo Renner wrote:
>>>> so I guess you both give a +1 one the patch which would outweigh
>>>> Olly's -1
>>> I am +1 for the patch but I am not sure we can override even a single
>>> -1 with several +1s... I would like that feature to be in core. Let's
>>> convince Olly that it is good to have ;)
>> Ok, ;)
>> the hideTable can increase the usability.
>> If you have an extension with many tables (e.g. mm_forum ~20). You don't
>> need them all, because there is special admin-interface. You only need
>> the two main-tables. So the author of an ext can make it easier for
>> everybody.
>> So if you really want to check worldshaking data, which should be in a
>> hidden table, you can use phpmyadmin or unset the TCA-hideTable-fag  ;)
>>
>> Same issue some flag 'hideInNewRecordItemList' (db_new). (This should be
>> an other patch, because this would be a new feature)
> 
> IMHO all pages that are hidden in the list module should also not appear
> in the NewRecord selector. What do you think?

I had a similar feeling some months ago... ;)
Search for the post "RFC: Integrate mod.web_list.deniedNewTables as
opposite of allowedNewTables" here in the Core list. Concerning the
difference between 'hide' and 'deny' here's my note the mentioned RFC:

> I think there are two separate cases:
> * if tables are hidden, this also implies to deny the create new button
> * if create new button is denied, it does not imply to hide tables
> 
> For the second case: It might happen that other functionalities create
> records of the affected table (e.g. a hook, IRRE, whatever) and it shall
> be insured that only these methods are able to create new records. But
> editing those records could be allowed, thus they are not hidden.


olly
-- 
Oliver Hader
http://inpublica.de/