[TYPO3-dev] hide be_user options by default?

Martin Kutschker Martin.Kutschker at n0spam-blackbox.net
Fri Feb 1 11:09:10 CET 2008


Dmitry Dulepov [typo3] schrieb:
> 
> There are two ways to do it: use type field or use conditions. As there 
> were no type field for this table, some exts could create one. If 
> another type field is added, it may break exts.

Oh come on. Every day devs add stuff to TYPO3 that *might* break an 
extensions. Fields are added, sometimes even changed (multi FE group access 
broke some extensions), etc.

The TCA layout (UI) of pages and tt_content have been changed. This WILL 
break extensions/setuos that modfiy the TCA in a certain way. You're 
proclaiming stagnancy.

Anway I habe thought up a way we're compatible in a reasonable way:

be_users gets a type or a checkbox "hide access lists", which defaults to 
"no". A new conf var may set the default to "yes". The new 1-2-3 installer 
will set this to yes, of course only for fresh installations.

If we want to we can change the above wording/semantics to a "show access 
lists" scenario.

Masi




More information about the TYPO3-dev mailing list