FuelPHP Forums

No, there isn't. But

$this->response->body = View::factory('errors/mine');
return;

will do the trick quite nicely. Note that CodeIgniter has a pretty straitforward front-to-back flow, so you can easily break out and stop. Fuel is more event driven, the fact that you stop a controller from execution doesn't stop everything around it (although this works fine for a main request). If you feel an extension of the error class is needed, please create a feature request at http://github.com/fuel/core/issues, explaining your reasons for wanting this feature.

Hmm... Considering the remark about CI's show_error(), I think the TS wants something that terminates the script, *like* a 404 exception, but with a view of his choice. What you could do is

throw new Request404Exception('views/this/that');

and then in your public/index.php

// Generate the request, execute it and send the output.
try
{
 $response = Request::factory()->execute()->response();
}
catch (Request404Exception $e)
{
 if ($e->getMessage() == '')
 {
  if ($route = Config::get('routes._404_'))
  {
   $response = Request::factory($route)->execute()->response();
  }
  else
  {
   throw $e;
  }
 }
 else
 {
  $response = new \Response(\View::factory($e->getMessage()), 500);
 }
}

Just make sure that view exists...

hmm... did I miss anything? Ah, change in the Error class. So the route is to define a custom exception that has this method, and then throw it? This seems to work:

<?php
class ApplicationException extends Exception {

 /**
  * Process the application error
  *
  * @return  void
  */
 public function handle()
 {
  ob_end_clean();
  echo \View::factory('errors/application', array('exception' => $this), false);
 }
}

Store this in app/classes/applicationexception.php. The view would be something like:

<?php
if ($m = $exception->getMessage())
{
    echo $m;
}
else
{
    echo "Put a generic error message here";
}

Then in your code you can use

throw new ApplicationException('any message you want to pass');

This is indeed 1.1 only. For 1.0, you could still throw the exception, and capture it in your index.php using a try/catch (see the 1.1 version of the index.php for an example). That way it will make the transition into 1.x easier as well...

You can avoid the notice by using

// only clean the buffer if it has any data in it
ob_end_length() and ob_end_clean();

I don't know of an easy way to find that out. But since you're triggering the error yourself by throwing the exception, you could pass something in the error message, or use the error code, to indicate what it is?

// throw a normal text error
throw new ApplicationException('this is a standard error');

// throw a json text error
throw new ApplicationException('this is a standard error', 1);

You can access the code you pass using the exception object's getCode() method.