Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fixing fatal error caused by Debugger not being loaded when viewing t…
…he default home page.
- Loading branch information
Showing
2 changed files
with
2 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3d966be
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually I'd suggest that's the wrong fix, there isn't really a circumstance whereby you'd want to show the contents of that file with debug == 0.
IME it's actually quite common if you don't create an app/views/pages/home.ctp file and either through lack of foresight or error (with routes config) expose the default home page on your live app.
Therefore, I'd propose the following as a more appropriate fix:
I also encourage other devs to create an appropriate or blank file in views/pages/home.ctp to prevent the default view from being reachable.
3d966be
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well the fix was to fix fatal errors because Debugger hadn't been loaded. But I see your point about both the baked home page, and the built-in one throwing exceptions.