Craft\CheckboxesFieldType » Craft\BaseOptionsFieldType » Craft\BaseFieldType » Craft\BaseSavableComponentType » Craft\BaseComponentType » Craft\BaseApplicationComponent » CApplicationComponent » CComponent
Craft\IComponentType, Craft\IFieldType, Craft\IPreviewableFieldType, Craft\ISavableComponentType, IApplicationComponent

Class CheckboxesFieldType

See also

View source

Public Properties

$behaviorsarray – The behaviors that should be attached to this component.

Protected Properties



protected boolean $multi = true

Public Methods

__call()Calls the named method which is not a class method.
__get()Returns a property value, an event handler list or a behavior based on its name.
__isset()Checks if a property value is null.
__set()Sets value of a component property.
__unset()Sets a component property to be null.
asa()Returns the named behavior object.
attachBehavior()Attaches a behavior to this component.
attachBehaviors()Attaches a list of behaviors to the component.
attachEventHandler()Attaches an event handler to an event.
canGetProperty()Determines whether a property can be read.
canSetProperty()Determines whether a property can be set.
defineContentAttribute()Returns the field’s content attribute config.
detachBehavior()Detaches a behavior from the component.
detachBehaviors()Detaches all behaviors from the component.
detachEventHandler()Detaches an existing event handler.
disableBehavior()Disables an attached behavior.
disableBehaviors()Disables all behaviors attached to this component.
enableBehavior()Enables an attached behavior.
enableBehaviors()Enables all behaviors attached to this component.
evaluateExpression()Evaluates a PHP expression or callback under the context of this component.
getClassHandle()Returns the component’s handle, ideally based on the class name.
getEventHandlers()Returns the list of attached event handlers for an event.
getInputHtml()Returns the field’s input HTML.
getIsInitialized()Checks if this application component has been initialized.
getName()Returns the component’s name.
getSearchKeywords()Returns the search keywords that should be associated with this field.
getSettings()Returns the component’s settings model.
getSettingsHtml()Returns the component’s settings HTML.
getStaticHtml()Returns a static (non-editable) version of the field’s input HTML.
hasEvent()Determines whether an event is defined.
hasEventHandler()Checks whether the named event has attached handlers.
hasProperty()Determines whether a property is defined.
init()Initializes the application component.
isInitialized()Checks if this application component has been initialized yet, or not.
isSelectable()Returns whether this component should be shown when the user is creating a component of this type.
modifyElementsQuery()Modifies an element query.
onAfterDelete()Performs any actions after a field is deleted.
onAfterElementSave()Performs any additional actions after the element has been saved.
onAfterSave()Performs any actions after a field is saved.
onBeforeDelete()Performs any actions before a field is deleted.
onBeforeSave()Performs any actions before a field is saved.
prepSettings()Preps the settings before they’re saved to the database.
prepValue()Prepares the field’s value for use.
prepValueFromPost()Returns the input value as it should be stored in the database.
raiseEvent()Raises an event.
setElement()Sets the element that the field type is associated with.
setIsFresh()Sets whether the field is fresh.
setSettings()Sets the setting values.
validate()Validates the field’s value.


Returns the field’s input HTML.

An extremely simple implementation would be to directly return some HTML:

return '<textarea name="'.$name.'">'.$value.'</textarea>';

For more complex inputs, you might prefer to create a template, and render it via {@link TemplatesService::render()}. For example, the following code would render a template loacated at craft/plugins/myplugin/templates/_fieldinput.html, passing the $name and $value variables to it:

return craft()->templates->render('myplugin/_fieldinput', array(
    'name'  => $name,
    'value' => $value

If you need to tie any JavaScript code to your input, it’s important to know that any name= and id= attributes within the returned HTML will probably get {@link TemplatesService::namespaceInputs() namespaced}, however your JavaScript code will be left untouched.

For example, if getInputHtml() returns the following HTML:

<textarea id="foo" name="foo"></textarea>

<script type="text/javascript">
    var textarea = document.getElementById('foo');

…then it might actually look like this before getting output to the browser:

<textarea id="namespace-foo" name="namespace[foo]"></textarea>

<script type="text/javascript">
    var textarea = document.getElementById('foo');

As you can see, that JavaScript code will not be able to find the textarea, because the textarea’s id= attribute was changed from foo to namespace-foo.

Before you start adding namespace- to the beginning of your element ID selectors, keep in mind that the actual namespace is going to change depending on the context. Often they are randomly generated. So it’s not quite that simple.

Thankfully, {@link TemplatesService} provides a couple handy methods that can help you deal with this:

  • {@link TemplatesService::namespaceInputId()} will give you the namespaced version of a given ID.
  • {@link TemplatesService::namespaceInputName()} will give you the namespaced version of a given input name.
  • {@link TemplatesService::formatInputId()} will format an input name to look more like an ID attribute value.

So here’s what a getInputHtml() method that includes field-targeting JavaScript code might look like:

public function getInputHtml($name, $value)
    // Come up with an ID value based on $name
    $id = craft()->templates->formatInputId($name);

    // Figure out what that ID is going to be namespaced into
    $namespacedId = craft()->templates->namespaceInputId($id);

    // Render and return the input template
    return craft()->templates->render('myplugin/_fieldinput', array(
        'name'         => $name,
        'id'           => $id,
        'namespacedId' => $namespacedId,
        'value'        => $value

And the _fieldinput.html template might look like this:

<textarea id="{{ id }}" name="{{ name }}">{{ value }}</textarea>

<script type="text/javascript">
    var textarea = document.getElementById('{{ namespacedId }}');

The same principles also apply if you’re including your JavaScript code with {@link TemplatesService::includeJs()}.


View source


  • $name (string) – The name that the field’s HTML inputs should have.
  • $values (mixed)


string – The input HTML.


public string getInputHtml ( $name, $values )


Returns the component’s name.

This is what your component will be called throughout the Control Panel.


View source


string – The component’s name.


public string getName ( )

Protected Methods

defineSettings()Defines the settings.
getContentPostLocation()Returns the location in POST that this field's content was pulled from.
getDefaultValue()Returns the default field value.
getOptionLabel()Returns an option's label by its value.
getOptions()Returns the field options, accounting for the old school way of saving them.
getOptionsSettingsLabel()Returns the label for the Options setting.
getSettingsModel()Returns the settings model.
getTranslatedOptions()Returns the field options, with labels run through Craft::t().
isFresh()Returns whether this is the first time the element's content has been edited.


Returns the label for the Options setting.


View source




protected string getOptionsSettingsLabel ( )