This article mainly introduces the use of plug-in controller features that ThinkPHP3.2.2 the latest support, very detailed, recommended for small partners.
The 3.2.2 version begins to support the call of the plug-in controller, which can be accessed through a more convenient URL address to a plugin-defined controller in the module.
When a plugin controller variable is passed in the URL, it is automatically positioned to the action method in the plug-in controller.
The variable of the plugin controller is set by the parameter Var_addon, which defaults to ADDON, for example, we pass in the URL:
Copy the Code code as follows:
Http://serverName/Home/info/index/addon/SystemInfo
Because the addon parameter is passed in, the user controller here is not the original
Copy the Code code as follows:
home/controller/infocontroller.class.php
Instead, it calls the Infocontroller controller of the SystemInfo plug-in (under the Home/addon directory), which is located
Copy the Code code as follows:
home/addon/systeminfo/controller/infocontroller.class.php
The plug-in controller itself is defined as the normal access controller, for example:
Copy the Code code as follows:
namespace Home\addon\systeminfo\controller; Class Infocontroller extends \think\controller{public function Index () { echo ' Addon SystemInfo '; }}
In this way, we are visiting
Copy the Code code as follows:
Http://serverName/Home/info/index/addon/SystemInfo
It will output when the
Addon SystemInfo
If our plug-in directory is not addon, but plugin, then we need to define it in the configuration file:
Copy the Code code as follows:
' Var_addon ' = ' plugin '
Then accessing the URL address becomes
Copy the Code code as follows:
Http://serverName/Home/info/index/plugin/SystemInfo
Note: The plug-in controller currently supports only the module's plug-in controller access and does not yet support the global public plug-in.
Note: This usage is only available for the 3.2.2 version downloaded from the official website. Subsequent adjustments will be made to the details, including defining the plug-in location and so on.