Re: How would I do this project best in CakePHP?

Yeah, you specified your groups in your OP:
- Users
- Editors
- Admins

Set Auth->authorize to controller and create an isAuthorized() action
in each controller which checks $this->Auth->user('user_group_id') and
returns true or false depending on if the user has access to the
actions they are trying to access.
http://book.cakephp.org/view/1275/authorize

HTH, Paul.

On Sep 28, 12:47 pm, "Yves S. Garret" <yoursurrogate...@gmail.com>
wrote:
> Why user_groups?  What is that for?  For permissions?
>
>
>
>
>
>
>
> On Wed, Sep 28, 2011 at 3:53 AM, WebbedIT <p...@webbedit.co.uk> wrote:
> > The way to develop any good solid app is to start with the database,
> > create models, then contorllers, then views and est voila you have an
> > app.
>
> > At it's most simple, you should have the following tables in your
> > schema:
> > - users
> > - user_groups
> > - teachers
>
> > I would then use Auth with $this->Auth->authorize = 'controller'; and
> > create an isAuthorized() action in each controller to check
> > authorisation levels depending on a users group.
>
> > HTH, Paul
>
> > On Sep 27, 9:40 pm, "Yves S. Garret" <yoursurrogate...@gmail.com>
> > wrote:
> > > Hi all,
>
> > >    I'd like some advice/direction on this.  I'm fairly new to Cake, so
> > this
> > > would be very much appreciated.  Basically, I have this assignment at
> > work
> > > (oh yeah, CakePHP will be our framework as we're going along in our
> > > department, something I'm not 100% familiar), where you have a website
> > that
> > > shows a list of names (last name and first name) and 3 code that mean
> > > something to the person searching for the person.  It's a list of
> > teachers.
>
> > >    Now, there will be 3 roles, Users, Editors and Admins.  Users can view
> > > data (no sign on is necessary). Editors can do what a User can do and add
> > > new names to the list, delete them and update them (there is a
> > requirement
> > > that you should be able to 'Enable' and 'Disable' teachers, essentially
> > they
> > > are not shown when searched for).  The Admin can do what an Editor can
> > do,
> > > add new Editors to the system and make the existing Editors also Admins
> > > (need to guard against an Admin from getting rid of his own privileges if
> > > he's the only one).
>
> > >    Now, I don't expect anyone to do this for me (what, you think I'm
> > going
> > > to let someone else have the fun :-) ?)  But the current tutorial seems
> > not
> > > really close to what I wanna do and since I'm not too familiar with
> > CakePHP
> > > and how it works, I'd like some pointers on this or -- even better -- a
> > > tutorial that's similar to what I am trying to do.
>
> > >    I'm already sketching out how the database will look as a start.
>
> > --
> > Our newest site for the community: CakePHP Video Tutorials
> >http://tv.cakephp.org
> > Check out the new CakePHP Questions sitehttp://ask.cakephp.organd help
> > others with their CakePHP related questions.
>
> > To unsubscribe from this group, send email to
> > cake-php+unsubscribe@googlegroups.com For more options, visit this group
> > athttp://groups.google.com/group/cake-php

--
Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions.

To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php