[Typo3-dev] RFC: New access control options

Karsten Dambekalns k.dambekalns at fishfarm.de
Mon Aug 9 14:05:50 CEST 2004


Hi Kasper,

On 2004-08-09, Kasper Skårhøj <kasper2004 at typo3.com> wrote:
> 2) You can now limit a user to select only certain values in any
> selectorbox; Here and now that is requested for content element types
> and also selection og plugins.
 ...
> - "explicitAllow" - if this mode is set all values cannot be selected
> - "explicitDeny" - if this mode is set all values can be selected by
> - "individual" - while the other two modes regards all values in the
 ...
> So, the question is; What mode should be the default in the next
> release? (Notice; Since this is just a question of configuration you can

I'd go for the explicitDeny as default. It changes little for those
who upgrade, giving less trouble (and load on the mailing lists). One
can change this if needed (only by an extension or in the
configuration as well?), so people can always switch, if the need to.

The problem of CE added by extensions is not a real one, I think. If
you apply tight control, in such a way that you limit the CE types
your users can access, you'd probably control the installed extensions
as well. When you install one, it should be not too much work to deny
access to it's CE types, if needed.

> I introduced two new render modes for selector boxes which means that
 ...
> Please see thsi screenshot and comment if you have any interventions
> before the 3.7.0 release.

Wow. *Very* nice IMHO.

Karsten




More information about the TYPO3-dev mailing list