Yes I use it a lot... only for a limited purpose but throughout the application.
I actually have two reasons for using it :) Reason 1: Yoy are close. Not email but similar componets none the less. I have my two components for sending mobile messages (sms and mms). The application does in some plugins scheduled newsletters. It can also be messages send by some system event (recieving a message for example can send an automatic reply) Reason 2: plugins. Everything in my app is plugins except a core doing common stuff. I use the PluginnameController in each to handle system integration. I could have chosen to load up a Pluginname model instead but since I very often need to be at the controller level (because of reason 1) there was little point. I don't use plugins at all as "standalone mini applications unrelated to the rest of the application" I use them much like normal desktop applications do. The core is independent of the plugins but each plugin relies heavily on the core for a lot of things. I would love to figure out some other good way to deal with plugin- interaction... so far requestAction is it. /Martin On Mar 26, 9:47 am, AD7six <[email protected]> wrote: > On Mar 26, 9:29 am, Martin Westin <[email protected]> wrote: > > > I did not catch this until I had scratched myself in the head for a > > good while. > > I thought it might help at least one other person avoid an uncommon > > problem. > > > 1.2.2 fixes a problem in AuthComponent that caused me some new > > problems. The fix is good, I just did not realise how it affected > > requestAction() and my personal convention for naming "request > > actions". > > Needing a convention implies you're using requestAction alot - why? > > > > > Auth does not like uppercase letters in action names. I was > > specifically using "SomeAction" as the action name for an action I > > call using requestAction. Just to make them stand out from normal > > actions. > > > The confusing things about finding out what had happened was: > > • being already logged into a session will still "allow" the action to > > run. > > • shell tasks (not logged in) would just stop (since new headers were > > set) without any error. > > I hope your shell is Email related (only 'valid' use for requestAction > imo :) ). > > AD --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
