1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
|
# Reference Plugins
FIXME The reference plugin is under development. Nothing to see here yet.
The Reference Plugin(s) are generic plugins that implement key pieces of the
Plugin Architecture.
They are broken down into several separate plugins, each covering different
portions of the [Hook API Reference](Plugin-Hook-API-Ref.md)
## Standard Files
The following files should be included in every plugin
* CHANGELOG
* INFO
* LICENSE
* index.php
* README.md
* setup.php
In general, the index.php file example below should be included in every plugin
directory as it prevents remote file browsing of your Cacti site.
```php
<?php
/*
+-------------------------------------------------------------------------+
| Copyright (C) 2004-2023 The Cacti Group |
| |
| This program is free software; you can redistribute it and/or |
| modify it under the terms of the GNU General Public License |
| as published by the Free Software Foundation; either version 2 |
| of the License, or (at your option) any later version. |
| |
| This program is distributed in the hope that it will be useful, |
| but WITHOUT ANY WARRANTY; without even the implied warranty of |
| MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the |
| GNU General Public License for more details. |
+-------------------------------------------------------------------------+
| Cacti: The Complete RRDtool-based Graphing Solution |
+-------------------------------------------------------------------------+
| This code is designed, written, and maintained by the Cacti Group. See |
| about.php and/or the AUTHORS file for specific developer information. |
+-------------------------------------------------------------------------+
| https://www.cacti.net/ |
+-------------------------------------------------------------------------+
*/
header("Location:../index.php");
?>
```
## File Structure
All plugin files should reside under their own respective plugin directory. The
example below is for a plugin called 'myplugin'.
```console
myplugin/
images/
myimage.png
index.php
lib/
index.php
functions.php
include/
index.php
settings.php
CHANGELOG
INFO
LICENSE
README.md
index.php
setup.php
```
## Contents of Files
The four core sub-directories included in your plugin should be docs, images,
lib, and include. As previously mentioned, each of these directories should
include an index.php that points to it's parent directory index.php. This way
we prevent people from randomly browsing the contents of our web site.
The two main files required for every plugin are the INFO and the setup.php
file. Without these two files, the plugin directory will not be recognized as a
valid plugin and will be skipped.
The INFO file is formatted as Microsoft standard INI file. It contains
information about the plugin including its version, author, dependencies,
functions, and minimum version of Cacti and other plugins required. Below, you
can see a reference INFO file for the myplugin plugin.
```console
[info]
name = mplugin
version = 1.0
longname = My First Plugin
author = Depeche Mode
email = somewhere@outthere.com
homepage = http://www.outthere.com
compat = 1.2
requires = thold monitor
capabilities = online_view:1, online_mgmt:1, offline_view:0, offline_mgmt:0, remote_collect:0
```
The setup file includes key plugin functions that allow the plugin to be
installed, uninstalled, upgraded, etc. Those core functions include:
```php
<?php
function plugin_myplugin_install() {
}
function plugin_myplugin_uninstall() {
}
function plugin_myplugin_check_config() {
}
function plugin_myplugin_upgrade() {
}
function plugin_myplugin_version() {
}
?>
```
Without these core functions, in your setup.php, your plugin will not fully
operate. We will document those functions and what they should include as we
continue to document the plugin design principals.
Any core plugin functions should always be placed in the lib/functions.php file,
and settings should go into the include/settings.php file. The plugin
architecture allows hooks to be defined that reach into the include/settings.php
file. Having those hooks point to the include version of the file will keep
Cacti page loads fast. Including too much in the setup.php slows Cacti and
should be avoided.
---
<copy>Copyright (c) 2004-2023 The Cacti Group</copy>
|
