1. • CommentAuthormakdaknife
   • CommentTimeSep 10th 2009

    
   I'm using Klevo's master off the github repository. Basically, I am looking to expand the user management component to make use of groups to control the level of access to different parts of the site. What I want to do is provide the following:
   - A user registration page
   - A login page
   - Some pages on the site that are only accessible to registered users within the 'subscribers' group
   - Lock the admin pages down to only allow access to 'administrators'
   
   I'm not sure if I should just do this by keeping the wf_users in a separate table, or if I should just modify how users currently work.
   
   I'm sure that someone else must have similar requirements... has anyone else built anything similar? And if you have, would you care to share your approach?
   
   Thanks
   Makdaknife
2. •  
     CommentAuthormajic
   • CommentTimeSep 10th 2009

    
   I would have a separate table for you subscribers - they don't need passwords they can be sent a link to unsub. unless they will be able to login for some other purpose which you have not explained.
   
   this may be a help to you (I have not read it through as yet)
   http://bakery.cakephp.org/articles/view/minimalistic-group-based-access-control-in-5-mins
   
   I like the idea of being able to have differing levels of users mainly admin get access to advanced features that may bewilder non-techie users That and locking down the access to other user accounts when not a super user
3. • CommentAuthorJaciss
   • CommentTimeSep 24th 2009

    
   I wrote something for this previously using Cake's acl framework and an AJAX GUI I found onlne - it's on my github fork of wildflower (user: Jaciss). You might have some issues applying my changes, as I haven't pushed any updates in quite some time. If this is something of interest I'll make it easier to use.
4. •  
     CommentAuthormajic
   • CommentTimeSep 26th 2009 edited

    
   Jaciss have you altered the db much -- I am going to see if I can create the groups and see if that gets my install of your fork working would be great if you could push some sql to github (still I may only be able table away)
   
   acl still has one over on me; guess I will have to wait for some sql; disabling the acl got revealed a number of interesting things
5. • CommentAuthorJaciss
   • CommentTimeSep 27th 2009

    
   Majic, I believe I put all db changes into the ruckusing system - the file's fairly self-explanatory:
   http://github.com/Jaciss/wildflower/blob/master/vendors/ruckusing/db/migrate/020_CreateWildGroupsTable.php
   
   You'll need the acl sql from Cake as well.
   
   I'll see about getting my fork updated and working this week, and post when I do.
6. • CommentAuthorTeckniX
   • CommentTimeSep 28th 2009

    

   Jaciss,
   I’ll look over your code, but may implement a simple group-based acl like so:

   http://bakery.cakephp.org/articles/view/minimalistic-group-based-access-control-in-5-mins

   Should be simple enough for now

7. •  
     CommentAuthormajic
   • CommentTimeSep 28th 2009 edited

    
   Pesky acl; a subject of much confusion to me variations of setup CRUD/Actions etc
   
   I have my aco/aro tree set I have granted permissions; but when I check in the console I get a horrendous error report
   
   Aro Tree
   

[1]Users

[2]dev

[3]admin

[4]admin

[5]registered

[6]reggie

[7]member

[8]anonymous


   
   Aco Tree (pages & root)
   
[1]controllers

[2]Dashboards

[3]Pages

[4]Categories

[5]Posts

[6]Comments

[7]Revisions

[8]Assets

[9]Uploads

[10]Messages

[11]Widgets

[12]Settings

[13]Utilities

[14]Users

[15]Groups






cake acl create aco root controllers
cake acl create aco controllers Dashboards
cake acl create aco controllers Pages
cake acl create aco controllers Categories
cake acl create aco controllers Posts
cake acl create aco controllers Comments
cake acl create aco controllers Revisions
cake acl create aco controllers Assets
cake acl create aco controllers Uploads
cake acl create aco controllers Messages
cake acl create aco controllers Widgets
cake acl create aco controllers Settings
cake acl create aco controllers Utilities
cake acl create aco controllers Users
cake acl create aco controllers Groups

cake acl create aro root Users
cake acl create aro Users dev
cake acl create aro Users admin
cake acl create aro admin admin
cake acl create aro Users registered
cake acl create aro registered reggie
cake acl create aro Users member
cake acl create aro Users anonymous

cake acl grant admin controllers/Posts create
cake acl grant admin controllers/Posts read
cake acl grant admin controllers/Posts update
cake acl grant admin controllers/Posts delete

cake acl grant admin controllers/Pages create
cake acl grant admin controllers/Pages read
cake acl grant admin controllers/Pages update
cake acl grant admin controllers/Pages delete

   
   clearly I am going wrong somewhere (perhaps all over the place with this)
   
   since in Jaciss's fork the wildflower/ is in use and controllers are name wild_* does this effect the aco/aro tree
   
   will update as/if I make progress
   
   updated the above;
   
   Edit:
   
   I have the acl plugin working; I have this working basic but working; happy happy joy joy. Will need to tidy it up before pushing it since I fiddled with submodules to try and resolve git wierdness with them (not totally happy with submodules)
   
   Thanks to Jaciss (great work -- it all works but does not send activation email -- unless it was spammed or I am too tired to notice something silly) also Technix for thoughts on this in the past
   
   onward make a reset password via email & sort that activation email
8. • CommentAuthorJaciss
   • CommentTimeSep 29th 2009 edited

    
   Yeah, I've about got my version updated and working as well, Majic. I forked the ACL code I used on github (and sent you a message), and will likely push my updates in the next couple of days. It definitely needs some love, but it does work.
   
   Edit: ohoh, and you're quite welcome. The issue with email might be a missing template. I'll look into it asap.
9. •  
     CommentAuthormajic
   • CommentTimeSep 29th 2009

    
   rewriting Phishy's ACL Plugin is a great idea (great minds think alike) - think the prototype used there overwirtes the existence of jquery which causes the error
   
   yeah a missing template could cause that the email to not send.
   
   >>It definitely needs some love, but it does work.
   yeah just a bit, and then the quirky hidden stuff too
10. • CommentAuthorJaciss
    • CommentTimeSep 30th 2009

     
    For those interested, I pushed to the acl branch on my Wildflower fork. Everything should be updated (no wild_ prefixes, updated ruckusing db info, ect). I believe the essentials are there and working, though there are still a few things that need work and testing before I'll feel comfortable sending out pull requests - probably tomorrow or the next day on that. It'll likely take a few more days of solid work before it's friendly for 'normal' users.
11. • CommentAuthorLouis
    • CommentTimeApr 5th 2010 edited

     
    [ never mind issue solved ]
    
    Thanks for the plugin.
    
    Louis

Wildflower CMS is the creation of Klevo
the Wildflower Logo was created by Oliver Treend