Looks like it's a bad idea to create handmade models named Aro and
Aco. When I change the model names (still referencing the default Cake
tables aros and acos, though), then I'm able to get the expected
results from my custom methods and properties. I chose AclRequester
and AclControlled as my model names. The only downside (so far), is
that I lose the AclNode functionality. So I'm manually bundling that
in my own custom behavior.
On Jun 3, 6:34 am, etipaced kevindecap...@gmail.com wrote:
In an attempt to utilize my own ACL system, I have 3 models which I
created:
- Aro
- Aco
- AclPermission
Each of these correlates with the default Cake ACL tables (aros, acos,
aros_acos, respectively). Now I'm trying to write some custom methods
in these models but having no luck. When attempting to access my
custom method through a controller model chain (NOT AuthComponent), I
get the following error:
1064: You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right syntax to use
near 'getAros' at line 1
In other words, even though I have a method named getAros(), I can't
call it. I'm happy to provide code if anyone is interested. I'm just
wondering if maybe I should call my Aro and Aco models different
names. I'm guessing they are automatically built-in and Cake is
disallowing me to customize their methods.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
CakePHP group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
