StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7477545
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-09-19T21:31:04.283
FavoriteCount
0
LastActivityDate
2011-09-19T21:31:04.283
LastEditDate
LastEditorUserId
0
OwnerUserId
953534
ParentId
7441907
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
First of all, you need to make sure you are loading your module by including it in the modules section of your application/bootstrap.php file like so <pre><code>Kohana::modules(array( 'my'=>MODPATH.'my' ) ); </code></pre> The fact that you mentioned going directly to the url for your error handler controller triggers a 404 error makes me think your module has not been loaded. I would also suggest a few more changes. http_response_exception.php does not need to extend Kohana_Exception, since this class is not an exception, but an exception handler. Along those same lines, a more appropriate class name might be Exception_Handler, since the class is not representing an exception, but handling them. Secondly, because of how you've named this file, it should be located in modules/my/classes/http/response/exception.php. Other than that, the code for this class looks ok. Similarly, because of how you've named your controller, it should be located and named a bit differently. Move it to modules/my/classes/controller/error/handler.php Remember that underscores in a class name means a new directory, as per <a href="http://kohanaframework.org/3.2/guide/kohana/conventions" rel="nofollow">http://kohanaframework.org/3.2/guide/kohana/conventions</a> Finally, I don't think you really need to extend the Kohana_Core class here, but instead just register your own custom exception handler. You can register your custom exception handler in either your application's bootstrap file, or in your module's init file with the following generic code: <pre><code>set_exception_handler(array('Exception_Handler_Class', 'handle_method')); </code></pre> Here's a customer exception handler I use, which is pretty similar to yours: <pre><code><?php defined('SYSPATH') or die('No direct script access.'); class Exception_Handler { public static function handle(Exception $e) { $exception_type = strtolower(get_class($e)); switch ($exception_type) { case 'http_exception_404': $response = new Response; $response->status(404); $body = Request::factory('site/404')->execute()->body(); echo $response->body($body)->send_headers()->body(); return TRUE; break; default: if (Kohana::$environment == Kohana::DEVELOPMENT) { return Kohana_Exception::handler($e); } else { Kohana::$log->add(Log::ERROR, Kohana_Exception::text($e)); $response = new Response; $response->status(500); $body = Request::factory('site/500')->execute()->body(); echo $response->body($body)->send_headers()->body(); return TRUE; } break; } } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow do I catch a HTTP_Exception_404 Error in Kohana
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAndrew Schmid
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COI am getting this error now: ErrorException [ Warning ]: set_exception_handler() expects the argument (Exception_Handler_Class::handle_method) to be a valid callback
 singulars
 PostPostId
 PO
 UserUserId
 USjnbdz

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.