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:
    name_of_the_pipeline name of the (...)

  • 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, (...)

  • Definition

    A pipeline is used to make one of SPIP’s standard functions perform different or additional functionality by passing it custom-made functions that (...)

  • 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 (...)

  • 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:
    icon path title (...)

  • The plugins cache

    There are some cache files specific to plugins which are also created in tmp/ or in tmp/cache/.
    plugin_xml.cache The results from analysing the (...)

  • 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 the (...)

  • 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, is (...)

  • 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: (...)

  • Installing external libraries

    Plpugins may also require external libraries that they are dependent upon to be downloaded. This requires several things: a specific declaration (...)

1 2