I wonder whether nested requestAction() calls is a good design decision. Sounds like a place for some refactoring / moving code to models. But as for turning off authComponent, couldn't you check your php_sapi_name() (http://ca.php.net/php_sapi_name) and go from there.
-Mark On Oct 19, 4:09 pm, jared <[EMAIL PROTECTED]> wrote: > I am curious if one of the core/more knowledgeable Cake guys can give > me some advice on either a better way to approach my problem or how to > approach working on a resolution. The issue I am having is that I have > many nested requestAction items that work like event observers. For > instance there is Item controller and the SubItem Plugin where the > write() function on the parent Item controller needs to also trigger > on the SubItem plugin if it is installed. At this point this works > well if the user is logged in. However, as soon as I try to write an > updating procedure from a Shell task this all halts. So part of the > problem I thought might be related to the Auth component with the > nested requestAction's not realizing that the current executing level > is actually from the shell. > > So, does anyone know of a way to programatically disable the Auth > component when the parent requestAction is being called from the shell > for itself and all of the child requestAction calls? > > Thanks, > jared --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
