Using Hook Behaviors in ThinkPHP: A Practical Guide

ThinkPHP defines a behavior as a key extension mechanism that can be invoked independently or attached to a tag for listening, similar to AOP concepts. Behaviors represent actions such as routing, caching, or permission checks that can be added without modifying core code.

The article introduces a simple login example where additional checks (mobile verification, captcha, etc.) would require modifying the controller each time, illustrating the need for decoupling logic using hooks.

Three behavior classes are defined:

// Connect.php
namespace app\index\behavior;
class Connect {
    public function run() {
        echo '连接网络';
    }
    public function __destruct() {
        echo '<br/>';
    }
}

// End.php
namespace app\index\behavior;
class End {
    public function run() {
        echo '关闭电脑';
        echo '<br/>';
    }
}

// On.php
namespace app\index\behavior;
class On {
    public function run() {
        echo '开启电脑';
        echo '<br/>';
    }
    public function qq() {
        echo '打开QQ';
        echo '<br/>';
    }
    public function opBrowser() {
        echo '打开浏览器';
        echo '<br/>';
    }
    public function app_end(&$param) {
        $param = '结束了';
    }
}

A controller (Index.php) binds these behaviors using Hook::add in its constructor and triggers them with Hook::listen :

namespace app\index\controller;
use think\Hook;
class Index {
    public function __construct() {
        Hook::add('app_init', [
            'app\\index\\behavior\\On',
            'app\\index\\behavior\\Connect',
        ]);
        Hook::add('qq', 'app\\index\\behavior\\On');
        Hook::add('opBrowser', 'app\\index\\behavior\\On');
    }
    public function index() {
        echo '我现在需要使用电脑进行社交';
        echo '<br/>';
        Hook::listen('app_init');
        Hook::listen('qq');
        Hook::listen('opBrowser');
    }
}

The article also shows how to define custom tags in tags.php for automatic binding, and presents the expected output screenshots illustrating the sequence of connected actions.

Overall, the guide demonstrates how ThinkPHP hooks enable modular, event‑driven extensions, allowing developers to add or modify functionality without altering core application code.