Hi all, This all seems a bit like reinventing the wheel to me ;)
Have you tried the cake db_acl solution? A great benefit of using the cake acl is the MPTT implementation - as soon as you have more than a trivial number of aros or acos you will probably find that, using what you have described here, your acl queries are slow and/or you have more aco than are necessary. The only thing that the cake acl won´t do for you by default is take care of a user being part of multiple groups, but you could get around that quite easily by querying the acl for the user and if that fails for each of the other groups the user is a member of (or just run the query for each group, if the acl granularity stops at groups). There is a plugin that allows you to manage things via a gui (albeit not so easy to setup, but it does work once you edit and include the config file somewhere apropriate - like in the plugin app controller), which isn´t too difficult to modify for administration. Anyway without going into too many details, creating aros like this: Article Article:Edit Article:Edit:1 It shouldn´t be too difficult to get the answer to "can X modify blog Y" with the minimum of execution time and aros in the db. HTH, AD7six --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
