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

Michael Stucki michael at typo3.org
Fri Aug 31 15:03:22 CEST 2007

Patch works fine, but I disagree about the logic:

| If $table tablename is found in $allowedNewTables and
| $deniedNewTables, $allowedNewTables has priority over
| $deniedNewTables.

IMHO "deny" must take precedence over "allow". Better restrict too much
and allow too few.

If someone wants to allow something but deny is set, he can use the
TSparser :=removeFromList() function.

- michael

Oliver Hader schrieb:
> This is a SVN patch request.
> Problem:
> TSconfig mod.web_list.allowedNewTables allows to define a set of tables
> which are allowed as new records on a page. mod.web_list.hideTables
> hides existing records on a page to be displayed but doesn't affect
> creating new records.
> Solution:
> Integrate the opposite of allowedNewTables: mod.web_list.deniedNewTables
> Documentation changes:
> In doc_core_tsconfig, Page TSconfig, section Web>List (mod.web_list):
> Create a new property after "allowedNewTables":
> * Property: deniedNewTables
> * Data type: list of tablenames
> * Description: If this list is set, then the tables listed here won't
> have a link to "create news" in the page and subpages.
> This also affects "db_new.php" (the display of "Create new record").
> This is the oposite of the previous property "allowedNewTables".
> If allowedNewTables and deniedNewTables contain a common subset,
> allowedNewTables takes precedence.
> Example:
> mod.web_list {
>   deniedNewTables = tt_news,tt_content
> }
> Branch: Trunk

Use a newsreader! Check out

More information about the TYPO3-team-core mailing list