Legacy Documentation

You are using the documentation for version 3.5.17. Go here for the latest version or check here for your available upgrades to the latest version.

Plugins¶

Tag Construction¶

A typical ExpressionEngine tag looks like this:

{exp:channel:entries}

The first segment is the tag identifier: {exp:. It tells the template engine that it has just encountered a tag.

The second segment is the “family” name: {exp:channel. There are different families of tags: channel, comments, members, email, stats, etc. In programming terms, the second segment is the name of the ‘class’ that is instantiated by the tag.

The above example would tell the template engine to dynamically instantiate the “channel” class.

The third segment indicates the ‘function’ from within a particular family of tags: {exp:channel:entries}. This example would tell ExpressionEngine you want to use the “entries” function in the “channel” class. To be more precise, the third segment is the “method” or “function” name within a given class.

A tag, therefore, mirrors an object oriented approach: Class->function:

{exp:class_name:function_name}

Note

Tags are not always required to have three segments. If your plugin is very simple you might opt to only use the class constructor. In this case you can get by only using two segments:

{exp:class_name}

Two Kinds of Tags¶

There are two kinds of tags: Single tags and tag pairs. A single tag does not have a closing tag:

{exp:randomizer:set_one}

Single tags are designed to return a single value. Tag pairs look like this:

{exp:xml_encode}
    Stuff between the tags
{/exp:xml_encode}

Tag pairs allow you to process the information contained between the tags. In the above example, the text between the pairs would be encoded with XML entities.

Anatomy of a Plugin¶

A plugin consists of a class and at least one function:

<?php if ( ! defined('BASEPATH')) exit('No direct script access allowed');

class Plugin_name {

    public function __construct()
    {

    }
}

/* End of file pi.plugin_name.php */
/* Location: ./system/user/addons/plugin_name/pi.plugin_name.php */

Note

Always deny direct access to your script by checking for the BASEPATH constant.

In addition, you should add some information that is displayed in the Plugin Manager section of the Control Panel. This is covered in the Control Panel Information section.

Creating a Plugin¶

The best way to learn how a plugin is created is to walk you through the process of creating one. For this example, we will create a plugin that prints “Hello World”. Our example plugin will have this syntax:

{exp:hello_world}

You will be able to use this plugin anywhere in a Template.

Creating the Plugin File¶

Once you’ve decided on a name for your plugin you will create a text file for it. The file name must be the same as the class name and it must have pi. as the prefix. We will name our file: pi.hello_world.php.

Plugin file names are always lower case and they must be identical to the name of the second segment of the tag:

{exp:hello_world}

Creating the Class¶

In the new file you’ve created add this class and constructor:

class Hello_world
{
    public function __construct()
    {

    }
}

Note

Class name must always be capitalized. This is the one exception to the rule. Tag names and file names are always lowercase, while the class name is capitalized.

Returning a Value¶

Your new class is useless unless it can return a value. There are two ways to return a value depending on whether your tag has three segments or two.

Two Segments¶

The above tag only has two segments therefore it only utilizes a constructor. Since constructors cannot return a value directly, we will assign it to a variable called: $return_data:

class Hello_world
{
    public $return_data = "";

    public function __construct()
    {
        $this->return_data = "Hello World";
    }
}

Three Segments¶

With tags that utilize three segments you can return directly. Consider a tag with this syntax:

{exp:hello_world:bold}

The third segment represents a function called bold, which can return a value directly:

class Hello_world
{
    public function bold()
    {
        return "<b>Hello World</b>";
    }
}

You could create a class with several functions this way:

class Hello_world
{
    public function normal()
    {
        return "Hello World";
    }

    public function bold()
    {
        return "<b>Hello World</b>";
    }

    public function italic()
    {
        return "<i>Hello World</i>";
    }
}

Each function would be accessible using these tags:

{exp:hello_world:normal}
{exp:hello_world:bold}
{exp:hello_world:italic}

Processing Data Within Tag Pairs¶

Often you will want to process data contained between a pair of tags. Let’s create a simple tag that makes text bold to illustrate how this is done. Our example plugin will have this syntax:

{exp:bold}
    Some text we want to process.
{/exp:bold}

You will be able to use this plugin anywhere in a Template. You can even put this tag within another tag in order to affect a variable:

{exp:channel:entries}
    {exp:bold}{title}{/exp:bold}
{/exp:channel:entries}

In following our naming rules, we will create a plugin file named: pi.bold.php. And we will create a class with this syntax:

class Bold
{
    public $return_data = "";

    public function __construct()
    {

    }
}

So how do we fetch the data contained within the tag pairs? Using the following variable:

ee()->TMPL->tagdata;

Here is how the variable is used:

class Bold
{
    public $return_data = "";

    public function __construct()
    {
        $this->return_data = ee()->TMPL->tagdata;
    }
}

Of course you’ll want to do something with the data before you return it, so let’s make it bold:

class Bold
{
    public $return_data = "";

    public function __construct()
    {
        $this->return_data = "<b>".ee()->TMPL->tagdata."</b>";
    }
}

Parameters¶

Since tags will often have parameters, the template engine makes it easy to fetch them using the following variable:

ee()->TMPL->fetch_param('param_name');

To see how this is used, let’s create a plugin that lets you format text based on the parameter. Our new plugin will have this syntax:

{exp:format type="uppercase"}
    Some text to process.
{/exp:format}

We will allow the following parameter choices:

type="uppercase"
type="lowercase"
type="bold"
type="italic"

Create a plugin file named pi.format.php and in it put this:

class Format
{
    public $return_data = "";

    public function __construct()
    {
        $parameter = ee()->TMPL->fetch_param('type');

        switch ($parameter)
        {
            case "uppercase":
                $this->return_data = strtoupper(ee()->TMPL->tagdata);
                break;
            case "lowercase":
                $this->return_data = strtolower(ee()->TMPL->tagdata);
                break;
            case "bold" :
                $this->return_data = "<b>".ee()->TMPL->tagdata."</b>";
                break;
            case "italic":
                $this->return_data = "<i>".ee()->TMPL->tagdata."</i>";
                break;
        }
    }
}

Passing Data Directly¶

ExpressionEngine allows any plugin to be assigned as a text formatting choice in the Publish page of the Control Panel. In order to allow a plugin to be used this way it needs to be able to accept data directly. This is how it’s done.

Add a parameter to the function. It’s best to make the parameter conditional so it will know whether it’s being used in a template or directly as a formatting choice:

class Bold
{
    public $return_data = "";

    function __construct($str = NULL)
    {
        if (empty($str))
        {
            $str = ee()->TMPL->tagdata;
        }

        $this->return_data = "<b>".$str."</b>";
    }
}

The above tag can then be assigned in the Publish page, allowing you to run your channel entries through it.

Database Access¶

ExpressionEngine makes it easy to access the database using the provided database class. To run a query you will use active record syntax:

$query = $this->db->get('mytable');
// Produces: SELECT * FROM mytable

To show the result of a query you will generally use the result_array array. This is an associative array provided by the database class that contains the query result. Let’s use a real example to show how this is used.

We will run a query that shows a list of members. For this we will create a plugin called pi.memberlist.php. The tag syntax will be this:

{exp:memberlist}

Here is the class syntax:

class Memberlist
{
    public $return_data = "";

    public function __construct()
    {
        $query = ee()->db->select("screen_name")
                ->get('members', 15);

        foreach($query->result() as $row)
        {
            $this->return_data .= $row->screen_name."<br>";
        }
    }
}

Here are some additional variables available in the database class:

$query->row()¶

If your query only returns one row you can use this variable like this:

$query = ee()->db->select('screen_name');
    ->get('members', 1);

return $query->row('screen_name');

$query->num_rows()¶

The number of rows returned by the query. This is a handy variable that can be used like this:

$query = ee()->db->select('screen_name')
    ->where('url !=', '')
    ->get('members');

if ($query->num_rows() == 0)
{
    $this->return_data = "Sorry, no results";
}
else
{
    $this->return_data .= sprintf(
        'Total Results: %s<br>',
        $query->num_rows()
    );

    foreach($query->result() as $row)
    {
        $this->return_data .= $row->screen_name."<br>";
    }
}

Control Panel Information¶

In addition to the class and function, you should also add some information that will display in the Plugin Manager section of the Control Panel. There are two parts to this information.

Plugin Information¶

Your plugin can describe itself in a little more detail by using a series of public static properties:

public static $name         = 'Member List';
public static $version      = '1.0';
public static $author       = 'Jane Doe';
public static $author_url   = 'http://example.com/';
public static $description  = 'Returns a list of site members';
public static $typography   = FALSE;

The information is as follows:

$name: The display name of the Plugin
$version: The Plugin version number
$author: The name of the Plugin author
$author_url: The URL associated with the author (or a URL to a page about the Plugin)
$description: A short description of the purpose of the Plugin
$typography: A boolean indicating if this plugin is used for text conversion

usage() function¶

The “usage” function is designed to easily allow you to give a description of how to use your new Plugin, including giving example ExpressionEngine code.

/**
 * Memberlist Class
 *
 * @package     ExpressionEngine
 * @category        Plugin
 * @author      Jane Doe
 * @copyright       Copyright (c) 2010, Jane Doe
 * @link        http://example.com/memberlist/
 */
class Memberlist
{
  public static $name         = 'Member List';
  public static $version      = '1.0';
  public static $author       = 'Jane Doe';
  public static $author_url   = 'http://example.com/';
  public static $description  = 'Returns a list of site members';
  public static $typography   = FALSE;

  public $return_data = "";

  // --------------------------------------------------------------------

  /**
   * Memberlist
   *
   * This function returns a list of members
   *
   * @access  public
   * @return  string
   */
  public function __construct()
  {
    $query = ee()->db->select('screen_name')
      ->get('members', 15);

    foreach($query->result_array() as $row)
    {
      $this->return_data .= $row['screen_name'];
      $this->return_data .= "<br />";
    }
  }

  // --------------------------------------------------------------------

  /**
   * Usage
   *
   * This function describes how the plugin is used.
   *
   * @access  public
   * @return  string
   */
  public static function usage()
  {
    ob_start();  ?>

  The Memberlist Plugin simply outputs a
  list of 15 members of your site.

  {exp:memberlist}

  This is an incredibly simple Plugin.


  <?php
      $buffer = ob_get_contents();
      ob_end_clean();

      return $buffer;
  }
}

ExpressionEngine® 3 User Guide

Plugins¶

Tag Construction¶

Two Kinds of Tags¶

Anatomy of a Plugin¶

Creating a Plugin¶

Creating the Plugin File¶

Creating the Class¶

Returning a Value¶

Two Segments¶

Three Segments¶

Processing Data Within Tag Pairs¶

Parameters¶

Passing Data Directly¶

Database Access¶

$query->row()¶

$query->num_rows()¶

Control Panel Information¶

Plugin Information¶

usage() function¶