[TYPO3-core] RFC: Integrate mod.web_list.deniedNewTables as opposite of allowedNewTables

Oliver Hader oh at inpublica.de
Wed Feb 28 08:34:10 CET 2007


Hi Masi,

Martin Kutschker wrote:
> Oliver Hader schrieb:
>> Ingo Renner wrote:
>>> Am 27.02.2007 um 10:40 schrieb Oliver Hader:
>>>> Solution:
>>>> Integrate the opposite of allowedNewTables:
>>>> mod.web_list.deniedNewTables
>>>
>>> wouldn't this be a new feature after feature freeze?
>>
>> Yes, indeed - this would be a new feature...
>> Without this missing feature developers/admins have currently no way to
>> prevent a record of a child table from being created directly. This
>> might mostly occur in consideration of IRRE.
> 
> What about my suggestion to disable the "new" buttons for tables that
> are hidden by "hideTables"? That's only a changed behaviour and creating
> records that disappear at once are no good UI anyway, so I cannot
> imaging someone wants "new" buttons for tables that are hidden.

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.

However, the patch file would stay the same - just "deniedNewTables"
will be replaced by "hideTables".


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


More information about the TYPO3-team-core mailing list