[TYPO3] user group configuration

Fri Oct 20 19:19:23 CEST 2006

You need to split it one step further:

Make editors your common group WITHOUT deny news, call it eg. "All-editors"

Make editor group with deny news and let it have All-editors as subgroup

Now you can also give Almost-admins the All-editors as subgroup and it will
not inherite the "deny news" property (because it is only in the "editors"
group.

Med venlig hilsen / Best Regards 

Franz Malten Buemann

Ordrupvej 114, DK-2920 Charlottenlund
T: 
+45 39 90 90 29
F:
+45 39 90 91 29
M:
+45 31 17 41 41
E:
info at t3p.dk
W:
www.typo3portal.dk

-----Original Message-----
From: typo3-english-bounces at lists.netfielders.de
[mailto:typo3-english-bounces at lists.netfielders.de] On Behalf Of Rakowski
Tomasz
Sent: 20. oktober 2006 18:50
To: typo3-english at lists.netfielders.de
Subject: [TYPO3] user group configuration

Hello list!

I have a small problem with user groups in BE:

there will be one suer-priviledged group in system, let's call those 
lucky ones 'almost-admin' group.
there is also another group, more limited in their actions, called 
'editors' group.

Because most of pages and content will be created by 'editors' but I 
want 'almost-admins' to have access to these sites I added 'editors' to 
  SubGroups of 'almost-admins' so 'almost-admins' can now modify 
anything created by the second group.

But I dont understand one thing: 'almost-admins' can put News ext on 
site as they dont have Deny News checked on Pagecontent: Plugin list 
whereas 'editors' are not allowed to do that, so Disable News is 
checked. But as turns out neither 'editors' nor 'almost-admins' can put 
this kind of ext as a page content. When I uncheck this Disable News in 
'editors' conf, plugin appears in the list of plugins possible to be added.

What is wrong? Thx for any help!

racco
_______________________________________________
TYPO3-english mailing list
TYPO3-english at lists.netfielders.de
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english