Installation¶

The google maps fieldtype is going to have 3 global settings. Latitude, longitude, and zoom. These will determine what the default map looks like. By returning an array from within install we can provide a default set of global settings.

function install()
{
    // Somewhere in Oregon ...
    return array(
        'latitude'  => '44.06193297865348',
        'longitude' => '-121.27584457397461',
        'zoom'      => 13
    );
}

Uninstaller¶

The installation method for this fieldtype does not create any additional tables, so no cleanup work needs to be done. The default uninstall() method provided by the EE_Fieldtype parent class will suffice. Most fieldtype methods have sensible defaults to help reduce duplicate code.

Global Settings¶

The installer sets the default global settings, but currently there is no way to change these from the control panel. We can use the display_global_settings() method to return the contents of the settings form. Having this method also enables the global settings link on the overview page.

function display_global_settings()
{
    $val = array_merge($this->settings, $_POST);

    $form = form_label('latitude', 'latitude').NBS.form_input('latitude', $val['latitude']).NBS.NBS.NBS.' ';
    $form .= form_label('longitude', 'longitude').NBS.form_input('longitude', $val['longitude']).NBS.NBS.NBS.' ';
    $form .= form_label('zoom', 'zoom').NBS.form_dropdown('zoom', range(1, 20), $val['zoom']);

    return $form;
}

Manually entering longitudes and latitudes is inconvenient so the final method in the example download also adds some javascript to let the user choose from a map.

Saving Global Settings¶

In most instances saving the global settings is as easy as storing the $_POST array. Remember to include existing global settings if not everything can be changed.

function save_global_settings()
{
    return array_merge($this->settings, $_POST);
}

Individual Settings¶

The default map may not always be the desired choice for each map field, so on the regular settings page it will display a similar configuration screen. We will use the familiar Shared Form View format to display our settings.

function display_settings()
{
    $latitude   = isset($data['latitude']) ? $data['latitude'] : $this->settings['latitude'];
    $longitude  = isset($data['longitude']) ? $data['longitude'] : $this->settings['longitude'];
    $zoom       = isset($data['zoom']) ? $data['zoom'] : $this->settings['zoom'];

    $settings = array(
        array(
            'title' => 'latitude',
            'desc' => 'latitude_desc',
            'fields' => array(
                'latitude' => array(
                    'type' => 'text',
                    'value' => $latitude,
                )
            )
        ),
        array(
            'title' => 'longitude',
            'desc' => 'longitude_desc',
            'fields' => array(
                'longitude' => array(
                    'type' => 'text',
                    'value' => $longitude,
                )
            )
        ),
        array(
            'title' => 'zoom',
            'desc' => 'zoom_desc',
            'fields' => array(
                'zoom' => array(
                    'type' => 'select',
                    'choices' => range(1, 20),
                    'value' => $zoom,
                )
            )
        ),
        array(
            'title' => 'preview',
            'desc' => 'preview_desc',
            'wide' => TRUE,
            'fields' => array(
                'preview' => array(
                    'type' => 'html',
                    'content' => '<div style="height: 300px;"><div id="map_canvas" style="width: 100%; height: 100%"></div></div>'
                )
            )
        )
    );

    // Map preview
    $this->_cp_js();
    ee()->javascript->output('$(window).load(gmaps);');

    return array('field_options_google_maps' => array(
        'label' => 'field_options',
        'group' => 'google_maps',
        'settings' => $settings
    ));
}

Saving Individual Settings¶

Saving individual field settings works largely the same as saving global settings. Keep be aware that they are later merged with global settings, so they can override a global setting.

If your fieldtype needs a wide style on the publish form, like Grid or a Textarea, then be sure to include 'field_wide' => TRUE in your settings array.

function save_settings($data)
{
    return array(
        'latitude'  => ee()->input->post('latitude'),
        'longitude' => ee()->input->post('longitude'),
        'zoom'      => ee()->input->post('zoom')
    );
}

Displaying the Field (Publish Page)¶

With all the settings set up, it can now be displayed on the publish screen. A key factor when you get to this stage is to decide in what format the data should be stored. Since all three available values in this case are numbers, this field will store them separated by pipes (lang|lat|zoom).

function display_field($data)
{
    $data_points = array('latitude', 'longitude', 'zoom');

    if ($data)
    {
        list($latitude, $longitude, $zoom) = explode('|', $data);
    }
    else
    {
        foreach($data_points as $key)
        {
            $$key = $this->settings[$key];
        }
    }

    $zoom = (int) $zoom;
    $options = compact($data_points);

    // some javascript

    $value = implode('|', array_values($options));
    $hidden_input = form_input($this->field_name, $value, 'id="'.$this->field_name.'" style="display: none;"');

    return $hidden_input.'<div style="height: 500px;"><div id="map_canvas" style="width: 100%; height: 100%"></div></div>';
}

Rendering the Tag¶

Finally, the field needs a frontend display. For google maps this will almost exclusively be javascript.

function replace_tag($data, $params = array(), $tagdata = FALSE)
{
    static $script_on_page = FALSE;
    $ret = '';

    list($latitude, $longitude, $zoom) = explode('|', $data);

    // google maps javascript ...

    return $ret.'<div style="height: 500px;"><div id="map_canvas_'.$this->field_id.'" style="width: 100%; height: 100%"></div></div>';
}

Creating Multiple Rendering Options¶

Along with parameters a field can also provide tag modifiers to change its output. In the template these are called by adding a colon to the fieldname, followed by the modifier name. For example: {myfield:latitude}. The advantage that field modifiers have over parameters is that they can be used in conditionals.

Parsing the modifiers is identical to using the regular replace_tag() function. The method name must start with replace_ followed by the modifier name.

function replace_latitude($data, $params = array(), $tagdata = FALSE)
{
    list($latitude, $longitude, $zoom) = explode('|', $data);
    return $latitude;
}

There is also a function to catch ALL modifiers, whose declaration includes the modifier name and looks like this:

function replace_tag_catchall($file_info, $params = array(), $tagdata = FALSE, $modifier)

You can also use variable pairs to capture tag data for processing in your modifier function. The syntax for using modifiers on variable pairs in your templates is:

{myfield:option}
    Tag data here
{/myfield}

Class Variables¶

The base class provides a handful of base variables:

property EE_Fieldtype::$EE¶

A reference to the controller instance.

property EE_Fieldtype::$id¶

The field identifier (unique for the current content type).

property EE_Fieldtype::$name¶

The field name, used for the tag names.

property EE_Fieldtype::$content_id¶

The unique id of the parent content that contains this field. Not available in install, settings, or other non-content environments.

property EE_Fieldtype::$content_type¶

property EE_Fieldtype::$settings¶

The field settings array

property EE_Fieldtype::$field_id¶

Alias for id

property EE_Fieldtype::$field_name¶

Alias for name

Function Reference¶

EE_Fieldtype::id()¶

Getter for id.

Return type:	Integer/String

EE_Fieldtype::name()¶

Getter for name.

Return type:	String

EE_Fieldtype::content_id()¶

Getter for content_id.

Return type:	Integer/String

EE_Fieldtype::content_type()¶

Getter for content_type.

Return type:	String

EE_Fieldtype::row($key[, $default = NULL])¶

Accessor for the current content type parent row. In the case of channel entries, this would be current entry row. If the key is not found, the value given in default is returned. Not all content types have all row keys.

Param:	string $key: The name of the row value to retrieve
Param:	mixed $default: The value to return if $key is not set
Returns:	The value of the row element, or $default.
Return type:	Mixed

EE_Fieldtype::install()¶

Installs the fieldtype and sets initial global settings. Can return an array of global variables.

Return type:	Void

EE_Fieldtype::uninstall()¶

Handle any cleanup needed to uninstall the fieldtype. Channel data is dropped automatically.

Return type:	Void

EE_Fieldtype::display_field($data)¶

Used to render the publish field.

Parameters:	$data (array) – Current field data, blank for new entries
Returns:	The field to display on the publish page
Return type:	String

EE_Fieldtype::validate($data)¶

Validates the field input

Parameters:	$data (array) – Current field data, blank for new entries
Returns:	TRUE if the field validates, an error message otherwise
Return type:	Boolean/String

EE_Fieldtype::save($data)¶

Preps the data for saving

Parameters:	$data (array) – Current field data, blank for new entries
Returns:	Data to save to the database
Return type:	String

EE_Fieldtype::post_save($data)¶

Handles any custom logic after an entry is saved.

Called after an entry is added or updated. Available data is identical to save. This is a good method to implement if you need the content ID of the fieldtype’s newly-saved parent content type.

Parameters:	$data (array) – Current field data, blank for new entries
Return type:	Void

EE_Fieldtype::delete($ids)¶

Handles any custom logic after an entry is deleted.

Called after one or more entries are deleted.

Parameters:	$ids (array) – IDs of deleted entries. Please note that channel data is removed automatically so most fieldtypes will not need this method.
Return type:	Void

EE_Fieldtype::pre_loop($data)¶

Before the tag is rendered on the frontend, this function is called to pass field data for the entire channel entries loop to the fieldtype for preprocessing or caching. This function is useful when your fieldtype needs to query the database to render its tag. Instead of querying with each loop of the channel entries tag, all data needed can be gathered up front, therefore reducing queries and loadtime needed.

Parameters:	data (array) – contains all field data for the current channel entries loop, limited only to the fieldtype’s own data
Return type:	Void

EE_Fieldtype::replace_tag($data[, $params = array()[, $tagdata = FALSE]])¶

Replace the field tag on the frontend.

Parameters:	$data (array) – contains the field data (or prepped data, if using pre_process) $params (array) – contains field parameters (if any) $tagdata (array) – contains data between tag (for tag pairs)
Returns:	String to replace the tag
Return type:	String

EE_Fieldtype::display_settings($data)¶

Display the settings page.

Parameters:	$data (array) – Field settings
Returns:	An array in the Shared Form View format
Return type:	Array

EE_Fieldtype::validate_settings($data)¶

Validate fieldtype settings. In this method, you can use the Validation Service to ensure values entered in your settings form are valid. Here is an example from our File field:

function validate_settings($data)
{
    $validator = ee('Validation')->make(array(
        'allowed_directories' => 'required|allowedDirectories'
    ));

    $validator->defineRule('allowedDirectories', array($this, '_validate_file_settings'));

    return $validator->validate($settings);
}

Callbacks may be specified as well, as you see above we are calling a method called _validate_file_settings to ensure upload destinations exist before creating a new file field.

Parameters:	$data (array) – Submitted settings for this field
Return type:	Validation result object

EE_Fieldtype::save_settings($data)¶

Save the fieldtype settings.

Parameters:	$data (array) – Submitted settings for this field
Returns:	Settings for the field
Return type:	Array

EE_Fieldtype::settings_modify_column($data)¶

Allows the specification of an array of fields to be added, modified or dropped when fields are created, edited or deleted.

Parameters:	$data (array) – settings for this field as well an indicator of the action being performed ($data['ee_action'] with a value of delete, add or get_info).
Returns:	Fields to be created, modified or dropped when fields are created
Return type:	Array

By default, when a new field is created, 2 fields are added to the exp_channel_data table. The content field (field_id_x) is a text field and the format field (field_ft_x) is a tinytext NULL default. You may override or add to those defaults by including an array of fields and field formatting options in this method. For example, the date file type requires an additional field_dt_x field and different content field type:

function settings_modify_column($data)
{
    $fields['field_id_'.$data['field_id']] = array(
        'type'      => 'INT',
        'constraint'    => 10,
        'default'   => 0
        );

    $fields['field_dt_'.$data['field_id']] = array(
        'type'      => 'VARCHAR',
        'constraint'    => 8
        );

    return $fields;
}

EE_Fieldtype::post_save_settings($data)¶

Do additional processing after the field is created/modified.

$this->settings is fully available at this stage.

Parameters:	$data (array) – submitted settings for this field
Return type:	Void

EE_Fieldtype::display_global_settings()¶

Display a global settings page. The current available global settings are in $this->settings.

Returns:	Global settings form
Return type:	String

EE_Fieldtype::save_global_settings()¶

Save the global settings. Return an array of global settings.

Returns:	Global settings
Return type:	Array

EE_Fieldtype::pre_process($data)¶

Preprocess the data on the frontend. Multiple tag pairs in the same weblog tag will cause replace_tag to be called multiple times. To reduce the processing required to extract the original data structure from the string (i.e. unserializing), the pre_process function is called first.

Parameters:	$data (array) – Field data
Returns:	Prepped $data
Return type:	Array

Grid Fieldtype Events¶

All of the regular fieldtype methods (display_field(), replace_tag(), etc.) are available prefixed with “grid_” for special handling when being used in the context of the Grid field, with a few exceptions noted below. For example:

// Only called when being used as a normal fieldtype:
public function display_field($data)
{
    // Display code
}

// Only called when being rendered in a Grid field cell:
public function grid_display_field($data)
{
    // Display code for Grid cell
}

However, if a fieldtype does NOT implement grid_display_field(), Grid will call display_field() to display the field’s form in the cell. This applies to all fieldtype methods except for the following:

The idea is that most fieldtypes should be able to use the same code to handle their field operations for both Grid and the normal publish form, but if not, you can easily override the behavior and run special operations when in the context of Grid.

If you use grid_* methods, you may want to look for ways to refactor your fieldtype where there is overlapping logic to run. For example, some of our native fieldtypes require slightly different code to render the HTML needed to display fields in display_field() and grid_display_field(), so we try to centralize the the common logic between them for better code maintainability.

Grid Fieldtype Settings Class Property¶

When your fieldtype is in the context of Grid, it will have a few more items available to you in your fieldtype’s $settings class property.

These are accessed as array keys of your $settings class property like so:

$this->settings['col_id'];

Grid Javascript Events¶

Several Javascript events are fired on certain actions to let your fieldtypes know when those actions have taken place. Here is an overview.

To bind an event, use the below Javascript as an example:

Grid.bind("date", "display", function(cell)
{
    // Act on event
});

Here are the usage details for this function:

Grid.bind(fieldtype, event, callback)¶

Arguments:	fieldtype (string) – Your short fieldtype name string – Event name callback – Callback function to use for the event
Return type:	Void

A jQuery object of the cell being affected by the current event (or settings form in the case of displaySettings) is passed to the callback function. There are a few data attributes available on the cell object such as fieldtype, column-id and row-id (row-id will be undefined for new rows). Plus since it’s a jQuery object, you have all DOM traversal methods available to act upon.

Fluid Fieldtype Settings Class Property¶

When your fieldtype is in the context of Fluid field, it will have an additional item available to you in your fieldtype’s $settings class property.

This is accessed as array keys of your $settings class property like so:

$this->settings['fluid_field_data_id'];

Fluid Javascript Events¶

Several Javascript events are fired on certain actions to let your fieldtypes know when those actions have taken place. Here is an overview.

To bind an event, use the below Javascript as an example:

FluidField.on("date", "add", function(element)
{
    // Act on event
});

Here are the usage details for this function:

FluidField.on(fieldtype, event, callback)¶

Arguments:	fieldtype (string) – Your short fieldtype name string – Event name callback – Callback function to use for the event
Return type:	Void

A jQuery object of the field being affected by the current event is passed to the callback function.

Live Preview Javascript¶

Live Preview automatically refreshes when HTML inputs, selects, and textareas are interacted with. If your fieldtype has other interactions that need to update the live preview, you can use the following JavaScript:

$(document).trigger('entry:preview');

Many fieldtypes do not need to be notified via JavaScript when the Live Preview modal opens and closes, many of your JavaScript bindings should continue to work. But certain libraries such as CKEditor may require some more attention in this area and for that you can listen to the entry:preview-open and entry:preview-closed events on $(document) to do any extra processing you need:

$(document).on('entry:preview-open', function(event) {
  // ...
});