Thats my point, no? How is a developer supposed to know which step core.php is loaded in the bootstrap process, in that it will cause problems. No ones going to know this unless they dig into the core files and discover it.
On Jun 22, 12:17 pm, AD7six <[email protected]> wrote: > On Jun 22, 7:20 pm, Miles J <[email protected]> wrote: > > > The problem is, its unclear when this error is thrown. I developed in > > Cake for over a year and still had this debug show in production. > > From your blog post: > > "debug in core.php was set to 2, and then disabled to 0 in > bootstrap.php" > > with hindsight you can see the problem with that - but it should be > obvious: That means any thing which happens generating a warning/error/ > notice inbetween loading core.php, and bootstrap.php will be sent to > users - and failing to connect to the db is one of those things in > cake 1.2/3. > > IMO what you describe in your blog post is a manufactured problem > _purely_ because you are sharing the same core.php file on your local > machine and your deployed site - don't do that. > > AD -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
