How to use CI framework to separate the front and back ends of the framework

This article mainly introduces the method of CI framework to realize the separation of front-end and back-end of the framework. It analyzes in detail the relevant views, controller settings and expansion of the front-end and back-end separation of CI framework in the form of examples. Friends in need can refer to it. Next

The example of this article analyzes the method of CI framework to realize the separation of front-end and back-end of the framework. Share it with everyone for your reference, the details are as follows:

When we develop using the CI framework (or develop using all other frameworks), we are always used to separating the front-end and back-end of the developed project. Place respective controllers, models or views in different folders. At this point, the ThinkPHP framework is more convenient than the CI framework. In this blog post, we will describe how to separate the front-end and back-end implementation based on CI framework development. (This article takes the Pkadmin backend management system developed by me as an example. The Pkadmin backend management system is developed based on the Codeigniter_v3.1.0 framework and the Olive Admin backend template. I will not introduce too much here. Interested friends can check it out on Github. Welcome Everyone corrects and learns from each other.

1. Establish a reasonable directory structure

I believe everyone already knows the directory structure of the CI framework and the functions of each directory. Here I won’t introduce it repeatedly (if you still don’t understand it well, you can read the blogger’s blog column). To realize the functional separation of the front-end and back-end frameworks, we must first establish a reasonable directory structure, that is, if you want to separate your Where should the front-end controller be placed, where should the background controller be placed, in which folder should the front-end view be placed, and in which folder should the background management view be placed.

As shown above It is the directory structure of the Pkadmin background management system. I put all the controllers in the controllers folder of the framework itself. I only added different front-end and background folders to store their respective controller files. The same is true for the views. No further details.

2. The extension loader sets the view path

① In order to have better maintainability of the project, I set the view path to a constant in App/config/constants.php Define constants in:

//定义前台视图路径常量
define('HOME_VIEW_DIR', 'views/Home/');
//定义后台视图路径常量
define('ADMIN_VIEW_DIR', 'views/Pkadmin/');
//版本
define('PKADMIN_VERSION', '1.0.0');

② Extension loader

How to extend the loader. If there are bloggers who don’t know how to do it, you can check out the CI framework. The manual is very clear. (One more thing: create the PK_Loader.php file in the APP/core folder)

<?php
/**
 * ==========================================
 * Created by Pocket Knife Technology.
 * Author: ZhiHua_W <zhihua_wei@foxmail.com>
 * Date: 2016/11/02 0031
 * Time: 上午 9:19
 * Project: Pkadmin后台管理系统
 * Version: 1.0.0
 * Power: 加载器扩展
 * ==========================================
 */
defined(&#39;BASEPATH&#39;) OR exit(&#39;No direct script access allowed&#39;);
class PK_Loader extends CI_Loader {
 /**
  * 设置前台视图路径
  */
 public function set_home_view_dir() {
  $this -> _ci_view_paths = array(APPPATH . HOME_VIEW_DIR => TRUE);
 }
 /**
  * 设置后台视图路径
  */
 public function set_admin_view_dir() {
  $this -> _ci_view_paths = array(APPPATH . ADMIN_VIEW_DIR => TRUE);
 }
}

3. Expansion controller

Extension controller is mainly for the convenience of generating parent controllers in the front and backend and for operation inheritance (for convenience, you can quickly understand the principle, the code has been streamlined).

<?php
/**
 * ==========================================
 * Created by Pocket Knife Technology.
 * Author: ZhiHua_W <zhihua_wei@foxmail.com>
 * Date: 2016/11/02 0031
 * Time: 上午 9:23
 * Project: Pkadmin后台管理系统
 * Version: 1.0.0
 * Power: 控制器扩展
 * ==========================================
 */
defined(&#39;BASEPATH&#39;) OR exit(&#39;No direct script access allowed&#39;);
/**
 * 前台父控制器
 */
class Home_Controller extends CI_Controller {
 public function __construct() {
  parent::__construct();
  $this -> load -> set_home_view_dir();
 }
}
/**
 * 后台父类控制器
 */
class Pkadmin_Controller extends CI_Controller {
 public $data;
 public function __construct() {
  parent::__construct();
  $this -> load -> set_admin_view_dir();
 }
}

#4. Test

Create a new Admin.php (backend home page) controller file in the Pkadmin controller folder for output Test (the code has been deleted and streamlined).

<?php
/**
 * ==========================================
 * Created by Pocket Knife Technology.
 * Author: ZhiHua_W <zhihua_wei@foxmail.com>
 * Date: 2016/11/05 0015
 * Time: 上午 10:23
 * Project: Pkadmin后台管理系统
 * Version: 1.0.0
 * Power: 后台主页控制器
 * ==========================================
 */
defined(&#39;BASEPATH&#39;) OR exit(&#39;No direct script access allowed&#39;);
class Admin extends Pkadmin_Controller {
 public function __construct() {
  parent::__construct();
  $this -> load -> model(&#39;login_model&#39;, &#39;admin&#39;);
  $this -> load -> library(&#39;pagination&#39;);
 }
 /**
  * Pkadmin 后台首页action
  */
 public function index() {
  $this -> load -> view(&#39;admin.html&#39;, $data);
 }
}

The background controller inherits the background parent class controller, and the front desk controller integrates the front desk parent class controller, the same Establishing the corresponding view files in the respective view folders is the perfect separation of the front and back ends.

The above is the entire content of this article. I hope it will be helpful to everyone's learning. For more related content, please pay attention to the PHP Chinese website !

Related recommendations:

About the implementation of infinite classification and recursion in the CI framework

About the CodeIgniter framework verification code class Analysis of library files and usage

How to solve 404 errors in Nginx and CI framework

The above is the detailed content of How to use CI framework to separate the front and back ends of the framework. For more information, please follow other related articles on the PHP Chinese website!