[TYPO3-ttnews] Help for planing feature "Category restriction at be_users/be_groups"
Ralf Merz
ralf at ralf-merz.de
Fri Nov 2 17:32:18 CET 2012
Hi Georg,
just by reading this, I guess it would be enough to control catagory
access only for be_groups.
I think it makes no sense to give be_users a group and then edit the
categories again in be_user.
But to give an answer for question 2, i think be_users selection should
be used, if it is set.
For question 3: In my opinion the selection should be recursive,
because mostly people use "Cat 2" only as devider. The behaviour should
be: if selecting "Cat 2", all sub-cats are selected and i may de-select
some, if i do not want to show them.
Just my 2 cents.
Regards
Ralf
On 2012-11-02 16:13:41 +0000, Georg Ringer <typo3 at ringerge.org> said:
> Hi,
>
> I am currently planing the mentioned feature because there are
> currently 2 sponsoring requests.
>
> I would like to get some feedback from you guys as there are many
> different ways how to achive that.
>
> The Questions I need to get answers too:
> - Should there be categories in be_users AND be_groups or only at one
> of the two?
> - If there is a category selection in be_users AND be_groups, which one
> should be used if both are filled?
> - Imagine a category tree like
> ----------------
> Cat 1
> Cat 2
> --- cat 2a
> --- Cat 2b
> ----------------
>
> and cat1 + cat2 are selected. should the child nodes "cat 2a" and "cat
> 2b" be selected as well or should that even be configurable somewhere?
>
>
> Thanks for some input!
>
> Georg
--
Ralf Merz
Dipl.-Ing. (FH)
merzilla
TYPO3 development, hosting, service
More information about the TYPO3-project-tt-news
mailing list