This is an old revision of the document!
Author: John Reese
Status: Work in Progress
The dynamic plugins system for Mantis is based on a philosophy of simplicity and lightweight design. It provides a very flexible framework for adding features to Mantis, or modifying certain existing functionality, using plugins. The system has been created to utilize an event-based hook system, but also allows plugins to create new view pages and more. Most anything that isn't directly allowed by the plugin system can easily be added on using the existing framework as a building block.
Rather than having each plugin execute and use the plugin API to set things up, the Mantis plugin manager uses the Inversion of Control design theories. This means that the core of plugins mostly consist of 'callback functions', usually discovered by the plugin manager at runtime. This greatly simplifies the work for the plugin developer, as it reduces the amount of necessary API calls from the plugin, as well as the amount of API functions the developer must know about. Considering the size of the rest of the Mantis API, this is a Good Thing.
Before going in depth with the inner workings of the plugin system, we will give an overview of the event system, which plays a critical role in giving plugins the flexibility and extensibility that they need. A full reference of the core events can be found in the Plugin Event Reference.
The Mantis event system requires all events to be 'registered,' by name and event type, before they can be used elsewhere. All of the core events are registered by default in
core/events_inc.php, but any plugin can declare their own events at startup. Once an event has been declared, callback functions may be 'hooked' to an event. These hooked functions will then be called by the event system whenever the hooked event is 'signaled'. The event type will determine how event parameters and callback return values are handled.
There are multiple event types defined in the core event system. Each one handles parameters and return values differently, and each event may have it's own specific usage of an event type.
This is the most basic event type in Mantis. When triggered, hooked callbacks will simply be called without any parameters, and their return values will be discarded. This will allow plugins to perform actions that do not directly affect the event originator.
This type of event is designed specifically for plugins to generate output that will be displayed to the user. The event is passed either a separator string, or an array of prefix, separator, and postfix strings; these strings will be applied to the hooked callbacks' output.
This event type is designed to allow plugins to process some input data one after the other, which each callback being passed the output from the callback before it. The parameter passed to the event becomes the input data for the first callback to process, and the return value of the last callback is returned to the event originator. In this method, actions such as output filtering are made simple.
The default event type is designed to be as flexible and generic as possible. The parameter to the event is passed directly to each hooked callback, and the return value from the callback is placed in an array with the callback name as the key. The resulting array is then passed back to the originator. Any event that doesn't fit one of the other event types can use this type to do anything.
This section covers the major topics needed to get started with plugin development. Anything else will be in the Advanced Topics section.
The most important step of getting a plugin to actually work with Mantis is properly advertising your plugin to the plugin manager, so that it may discover your plugin and allow the administrator to install it. This is done not only by creating the proper directory structure for your plugin, but by creating the right files with the right callback functions. Due to the use of Inversion of Control, you need not know much of the Plugin API to accomplish this task.
An example plugin with just the basic structure and registration can be seen with the Super Cow Powers sample.
In order to have a valid plugin, you must choose a succinct, one-word 'basename' for your plugin. This basename should only contain upper- and lower-case letters, dashes, and underscores, and should not include versions or anything more specific than the plugin name. You must then create a directory in the
plugins/ directory of Mantis with this basename, which will contain everything for your plugin. You will also need to have a file in this directory named
register.php, which will both provide Mantis with the appropriate information and form the core of your plugin.
A barebones plugin named
testing will have a structure like this:
plugins/ testing/ register.php
This is the single most essential file for a plugin; Mantis will look for this file in your plugin directory, and it must contain two specific callback functions:
This callback must exist for Mantis to recognize your plugin, and it gives your plugin the chance to tell Mantis more about itself, including its name, authors, and dependencies. This function must return an array of key/value pairs with some (or all) of the following items:
name- Your plugin's full name.
description- A full description of your plugin.
version- Your plugin's version string.
author- Your name, or an array of names.
contact- An email address where you can be contacted.
url- A web address for your plugin.
page- The name of a plugin page for further information and administration.
requires- An array of key/value pairs of basename/version plugin dependencies. Prefixing a version with
'<' will allow your plugin to specify a maximum version (non-inclusive) for a dependency.
This callback allows your plugin to set itself up, include any necessary API's, declare or hook events, etc. The only restriction is that anything beyond basic setup should be extracted to a callback hooked to
EVENT_PLUGIN_INIT, in order to lessen the task of registering plugins.
For plugins that need to hook many events at startup, this callback can be created to return an array af event name/callback pairs, and the plugin API will automatically handle hooking each pair.
The event system is what makes Mantis plugins flexible and extensible. Events can be utilized in many ways and from many locations, but there is a standard 'acceptable' method suggested for using events within plugins.
To conform to the recommended event usage patterns, there should be a file in in your plugin's root directory named
events.php, which should contain all of the hooked events' callback functions.
Building from the example above, your plugin should have the following structure:
plugins/ testing/ events.php register.php
This file will be included automatically by Mantis at runtime, but only when an event hooked by your plugin has been triggered. Therefore, you should not rely on this file to do anything but declare functions of the following form:
This is the generic format for hooked event functions. The
event parameter will be passed the entire event name, to differentiate between calls from multiple events.
params is an arbitrary value passed by the event originator, and may vary wildly depending upon the event type and the specific event being hooked. The value this function should return may also vary by event type and the event itself. Documentation for core events (and especially that of events from other plugins) should be read carefully to properly receive and return values.
The simplest way for a plugin to hook a function to an event is by calling
plugin_event_hook( event, function ), passing the full event name and the
<function> portion of the callback function from the section above. An event can be hooked at any time, even after the normal hook initialization. Once you've hooked the event, your function will be called whenever the event is triggered. For plugins that need hook many events or callbacks at once, there is a convenience function
plugin_event_hook_many( array ) which takes an array of event name keys mapping to callback functions.
Events must be declared before they can be used, with not only the event name, but the event type, which determines how its callback functions will be handled. Although the core Mantis system has declared and uses many events already, plugins can declare their own events as well, and trigger them as needed.
This function will declare a single event with a given name and type. The only types currently allowed are:
<?php event_declare( 'EVENT_PLUGIN_TESTING_1', EVENT_TYPE_DEFAULT );
This function will declare multiple events at once, taking a key/value array of event name/type pairs. For example:
<?php event_declare_many( array( 'EVENT_PLUGIN_TESTING_2' => EVENT_TYPE_EXECUTE, 'EVENT_PLUGIN_TESTING_3' => EVENT_TYPE_OUTPUT, ) );
In order to make plugins more accessible and available to international users, plugins can utilize the benefits of the Mantis language system to consolidate text into separate files for each language, allowing the plugin to be easily translated for different languages.
Using international language strings in plugins is just as easy as it is in the core Mantis system. A simple call to
lang_get( string ) is enough to have the named string displayed in the user's language of choice, assuming the necessary translation file is available. If the plugin has not yet been translated to the needed language, the English language strings will be used by default.
If your plugin needs to use language strings that aren't already declared by the core Mantis system, it is very simple to provide the appropriate language files with your plugin. All language files need to be named
'strings_<language>.txt', and must be in the
lang/ folder in your plugin's root directory.
Drawing on the example plugin used above, the structure should follow this pattern:
plugins/ testing/ lang/ strings_english.txt strings_german.txt events.php register.php
The language file itself should follow the same format as standard Mantis language files, a PHP script that declares strings in the following pattern:
<?php $s_plugin_testing_title = "Testing Plugin"; $s_plugin_testing_manage = "Manage Plugin";
The above string would then be displayed using something like the following code:
<?php echo lang_get( 'plugin_testing_title' );
Many plugins will likely have some elements that can or need to be configurable by the site admin or end-user, such as access thresholds or behavioral preferences. As Mantis has a powerful configuration system already, plugins can take advantage of the existing configuration system by using the plugin API, which will ensure simplicity and separation of configurations between multiple plugins.
To allow the usage of default configurations for plugins, developers can create a callback method in the plugin's
register.php file named
plugin_callback_<basename>_config(). This callback should return an array of configuration option name/value pairs, which will be set as default global configuration values. These values will be overridden by any value stored in the database as shown below, so any persistent configuration will not be affected.
To retrieve a plugin configuration value, your plugin can call
plugin_config_get( name ) to get value from the database (if explicitly set), or from the default configuration as explained above. In order to store configuration values in the database, your plugin will need to call
plugin_config_set( name, value ), which will create or overwrite the existing value. After this call, then any subsequent call to
plugin_config_get() should return this value.
In order to create entirely new features, plugins must be able to create new pages without needing to worry about all of the Mantis core API. For this reason, the Mantis plugin system includes a very simplified method for structuring and linking to plugin pages.
Plugin pages can be named and structured as needed, but they must all be located in the
pages/ subdirectory of the plugin root.
Using the above example plugin as a basis, new pages can be created in the following pattern:
plugins/ testing/ lang/ strings_english.txt strings_german.txt pages/ about.php manage.php events.php register.php
Once a page has been created, it can be linked to by using the
plugin_page( page ) function to generate the appropriate URL. If a link is needed to another plugin's page, the
plugin_page( page, plugin ) function form can be substituted. By using this generated link, you page does not need to deal with locating and calling the core API's to initialize Mantis, and it can simply start with the actual code needed for the page.
This is an example of a basic display page, which outputs the standard Mantis header and footer, but does nothing else:
<?php html_page_top1( lang_get( 'plugin_testing_title' ) ); html_page_top2(); # Create a basic href link to the manage.php plugin page echo 'A href="', plugin_page( 'manage' ), '">', lang_get( 'plugin_testing_manage' ), '</a>'; html_page_bottom1( __FILE__ );
In order to allow more advanced plugins the ability to handle the process of installing, upgrading, or uninstalling, the Mantis plugin system has defined some custom callback functions for each task:
This callback is executed before the normal plugin installation process has started. This should be used for checking conditions in Mantis to see if the plugin can be used, or for other general setup procedures. /This callback must return TRUE if the installation should continue, or FALSE if installation should be halted./ This allows your plugin to prevent installation in case of errors or other hazardous situations.
This callback is executed after the normal schema upgrade process has executed. This gives your plugin the chance to convert or normalize data after an upgrade. Your callback will receive a single parameter: the schema version from *before* the upgrade took place, allowing your plugin to know how much upgrade work needs to be done (eg. switch/case statements are perfect here). /By definition of the install process, this function will also be called during installation when the plugin schema is 'upgraded' from nothing./
This callback is executed after the normal uninstallation process, and should handle such operations as reverting database schemas, removing unnecessary data, etc. This callback should be used only if Mantis would break when this plugin is uninstalled without any other actions taken, as users may not want to lose data, or be able to re-install the plugin later.