Good point. But wouldn't a 500 be better than a 404? Not that big a deal, but the 404 just had me all hung up looking for routing mistakes when that was nowhere near the problem.
\\Ryan Sent from my iPhone On Dec 19, 2008, at 9:08 PM, mark_story <mark.st...@gmail.com> wrote: > > Well you did put the debug off, so all nice error messages turn into > 404's. Wouldn't be a good idea to leave all the nice errors so an > site visitor/attacker could see your mistakes :) > > -Mark > > On Dec 19, 5:52 pm, RyOnLife <ryan.mckil...@gmail.com> wrote: >> Go figure. 3 hours of trying and the moment send my previous message: >> it hits me. Clear the models cache. I'd added a new table. That fixed >> it. Wish Cake had some better error handling in that case. Would >> opening a ticket for that "issue" be appropriate? >> >> On Dec 19, 5:41 pm, RyOnLife <ryan.mckil...@gmail.com> wrote: >> >>> My app suddenly went haywire. When I set debug to 0, I get 404 not >>> found errors (from Cake, not Apache) on all pages. With the debug >>> setting at 1 or 2 there are no problems. I've been working on this >>> app >>> for months and have never had a problem when changing debug mode >>> to 0. >>> I haven't made any edits to routes.php, any .htaccess files or to >>> Apache configuration. >> >>> Any ideas? Does Cake inherently handle routes differently when debug >>> is on/off? > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
