Sorry, I had to ask. That was one of the things I god stuck on a bit at first. The only thing I can think of that is totally dependent on the Debug- level is the way you output the data. This is also a very simple thing you probably checked and re-checked. I have set autoRender to false (when returning simple ack type messages I do not bother rendering) and output the result of my actions using "echo".
Also, for me, setting debug higher than 0 causes my remote api to fail. Yours should too if you are doing anything similar. With debug higher than 0, Cake outputs some debug information with every request, eg: "true<!-- 0.211s -->", so I do not get the result I expect. You should see the timestamp (if you are reading the plain source) But why you are outputting nothing is strange indeed. On May 13, 9:24 am, David Christopher Zentgraf <[EMAIL PROTECTED]> wrote: > No, I'm explicitly allowing the remote action. > I thought about the being-logged-in scenario as well, but that's not it. > > As written before, when setting the Debug level to 0 it stays quiet, > when setting it to 1 it works as it's supposed to. > > And I always got a HTTP/1.1 200 OK. > > I'm still baffled. > > On 13 May 2008, at 16:14, [EMAIL PROTECTED] wrote: > > > I do exactly what you describe. calling one CakeApp from another using > > file_get_contents() and... it work perfectly. > > > General advice: > > Security? have you set it to anything other than the defaults? Is the > > remote action login-protected? > > > I ask since you say it works in the browser... and your browser will > > probably already be logged in, accepted as a UA with a running > > session. Curling to the url and you will be a fresh session. > > > Try > > curl -Ihttp://example.com/controller/action > > You should see http status 200. If you see anything else 302 (probably > > login redirect), 401 (authentication needed). Anyway, you should see > > something other than an OK 200 response. > > > On May 13, 6:31 am, David Christopher Zentgraf <[EMAIL PROTECTED]> > > wrote: > >> Okay, that's weird. > >> Setting Debug to 1 in core.php suddenly gives me an output. > >> Even though in my remote action I explicitly call: > > >> $this->layout = 'ajax'; > >> Configure::write('debug', 0); > > >> Interestingly, if I set debug to 0 in core.php and try to turn it > >> back > >> on in my action, it doesn't work either. > > >> Now I have even more questions. ;-) > >> Why is the debug level suppressing my output, > >> and how can I get it to output something without turning debug on for > >> the whole app? > > >> Chrs, > >> Dav > > >> On 13 May 2008, at 13:15, Dr. Tarique Sani wrote: > > >>> I am presuming that you have set Debug to 0 - what happens when you > >>> turn the > >>> debug level up? > > >>> T > > >>> -- > >>> ============================================================= > >>> Cheesecake-Photoblog:http://cheesecake-photoblog.org > >>> PHP for E-Biz:http://sanisoft.com > >>> ============================================================= --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
