WHM plugins add new functionality to the WHM interface.
- cPanel plugin requirements and WHM plugin requirements are not identical. For information about cPanel plugins, read our Guide to cPanel Plugins documentation.
- For help to troubleshoot issues with WHM plugin development, read our Guide to Testing Custom Code documentation.
cPanel & WHM versions 64 and 66 included major updates to the WHM interface that affect most WHM plugins. If you developed your plugin for cPanel & WHM version 62 or earlier, you must update it.
- For additional information, read our Create a WHM Plugin tutorial.
- Make certain that your applications respect user privacy. We strongly recommend that you anonymize any data that you collect for analysis. For more information about how cPanel, L.L.C. handles private data, read our cPanel Analytics documentation.
When you create a WHM plugin, we recommend the following workflow:
- Create your custom application (the plugin's backend code).
- Create the plugin's interfaces and other files .
- Create an installation script. This script should register your plugin with AppConfig and perform several other actions.
- Create your plugin's AppConfig configuration file.
Compress your plugin's files for distribution.
We recommend that you compress your plugin's files into a tarball (
.tar.gz) file for ease of distribution.
- For most plugins, the compressed file should contain the application source files, the AppConfig configuration file, an upgrade script, and an installation script.
- We recommend that you compress your plugin's files into a tarball (
Distribute your plugin. When you distribute this plugin across multiple servers, system administrators must perform the following actions manually:
Decompress the plugin's
- Run the installation script.
- Decompress the plugin's