plugin.xml
Articles
Using pipelines
To use the pipelines of SPIP or of a plugin, their usage must be explicitly defined in the plugin.xml file: xml name_of_the_pipeline name of (...)
The basic principle of plugins
Plugins add features or functions to SPIP, which might be a set of standardised template files, a modification of existing functionality, (...)
Installing external libraries
Plpugins may also require external libraries that they are dependent upon to be downloaded. This requires several things: a specific declaration (...)
Defining page tabs
Declaring the tabs for the exec pages in the private zone follows exactly the same syntax as for the buttons. The name of the parent, however, (...)
ajouter_onglets
Adds tabs to the pages of the private area
Defining buttons
To add buttons into the private zone, all that is needed is to provide a bouton element in the plugin.xml files as follows: xml icon path (...)
Handling dependencies
Plugins can indicate if they depend upon certain conditions in order for them to work correctly. Two attributes are used to specify this: (...)
plugin.xml, other common attributes
Options and functions
The files for the options and functions provided by the plugin are declared directly within the plugin.xml file using (...)ajouter_boutons
Adds buttons to the menu bar in the private area
The minimal plugin.xml
The plugin.xml file must be created in the root directory of your plugin. It contains the description of the plugin and allows it to define (...)