These core updates represent a shift in the expectation of CodeIgniter. They implement some convention, instead of CI-style configuration. They're not for everyone but definitely for me.
Method names have been updated to include a METHOD prefix. Typically, that means you'd be prefacing methods with get_, however post_, put_, and any other valid request methods are valid.
<?php
class Posts extends MY_Controller {
public function get_index() {
// ...
}
}Two filters are added to all controllers, before and after. They may be defined as a single method, an array of methods, or a protected method.
<?php
class Posts extends MY_Controller {
protected $before_filter = 'log_views';
protected $before_filter = array('log_views', 'check_auth');
protected function before_filter() {
}
protected $after_filter = 'clear_sessions';
protected $after_filter = array('clear_sessions', 'cleanup_tmp');
protected function after_filter() {
}
}View loading is now automated and therefore called after every controller method. The name of the view is inferred from the class name and the method name. So, Posts::get_index() would load a view: posts/index and Users::post_confirm() would load users/confirm. You can override this by setting the view class variable.
<?php
class Posts extends MY_Controller {
public function get_index() {
// ... loads view: posts/index.php
}
public function get_index() {
$this->view = 'blog/index';
// ... loads view: blog/index.php
}
}To pass data to a view simply set the variable as a member of the controller class. Any class variables set after __construct runs will be passed to the view.
<?php
class Posts extends MY_Controller {
public function __construct() {
$this->lib = // ... not passed to view
}
protected function before_filter() {
$this->sidebar = // ... passed to view
}
public function get_index() {
$this->posts = // ... passed to view
}
}To skip automatic view loading return any non-false value from your controller. That value will then be rendered to the page.
By default, all views are loaded within a global application layout. The layout is defined by the protected class variable $layout and defaults to application/layout.
The layout is rendered with the contents of the sub-view contained within the $yield variable. In addition, the layout has access to any class variables defined within the controller method or the sub-view.
<?php
// controllers/posts.php
class Posts extends MY_Controller {
public function get_index() {
$this->posts = // ... passed to view and layout
}
}<!-- views/posts/index.php -->
<?php $this->title = 'test'; ?>
<div> ... </div><!-- views/application/layout.php -->
<html>
<head>
<title><?=$title?></title>
</head>
<body>
<?=$yield?>
</body>
</html>A few common headers are automatically applied to all requests.
The Content-type header defaults to text/html unless it is overridden in the controller or via a URL suffix. In the controller it is overridden with the class variable $content_type. As a URL suffix the file extension is mapped to a mime type via the application/config/mimes.php mappings. If multiple mime types are present for a particular extension the first one listed will be used.
<?php
class Posts extends MY_Controller {
protected $content_type = 'application/xml'; // ... all methods default to xml
public function get_index() {
$this->content_type = 'application/json'; // ... this method returns JSON
}
}Using URL suffixes a request to posts/index.json would return a JSON array of posts given the following controller:
<?php
class Posts extends MY_Controller {
public function get_index() {
return $this->db->get('posts')->result_array();
}
}The Cache-control header defaults to no-cache, disabling any client side caching of HTML. You may override this however you like by setting the $cache_control class variable.
This header also sets the, similar, Edge-control header with whatever is set for Cache-control.
<?php
class Posts extends MY_Controller {
protected $this->cache_control = 'max-age=86400, public';
public function get_index() {
$this->cache_control = 'max-age=300, public';
}
}Of note: If the content_type is set to text/json errors and data returned
from your controller will be automatically wrapped in json_encode().
Any exceptions thrown and not caught during execution of the controller method, the before, or the after filters will be presented within the CI show_error function. The method will be passed the getMessage() value of the exception.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent