Closed sergeyklay closed 11 years ago
Can you explain your ideas if possible?
First, I think it is wrong that in the absence of access, triggered exception or throws (403, 404, etc.). But I think we need to to log such events. Maybe, if the user is not logged in, it makes sense to redirect the authentication page
Many cases we need to throw 404 or 403 and in few cases we need to redirect to login form if not logged in.
In general, the fundamental idea is to add ability a callback method as an argument to ACL::required()
I think we can add ACL::redirect cases where we need redirect to another page or login
I looked similar implementation in Zend and Symfony and I found that we could borrow a something
Maybe worth paying attention to the ready-made solutions for similar problems:
Hi all!
@sandeepone
I have some ideas about ACL 2.0 that you can look at this url: https://gist.github.com/sergeyklay/5075595
Here's one way how we can use this: https://gist.github.com/sergeyklay/5075608 But this is not the only change in the ACL class, and this is beta version
I seriously reworked the code and add new methods. And I'm interested in your opinion
@dishuostec
If you have anything to add - it would be good
Best regards,
also see: 68b60b7123f9fbeae4dc5cf5d44edb666f7cf140 5da99fe01d17a4a955ecdc7b78c24afd7442d33f a4b8b0339004b84e6e40add048a7f6161e4783fa 0abe2a3a545c67b714d14ad60ae53ab058057bef d35b32604178cfb80721886886195deef7f4ead0
Sorry, I didn't follow this issue, but we've covered most of the things.
yep!
I have some ideas on ACL... I think I could improve it. Let me move it in a separate module (may be Gleez ACL) to improve it