Skip to main content
Version: 4.3

Inplace editable

Draft document
This documentation is currently in-progress. You can help by contributing edits to this page.

The inplace_editable element is a mini-API which allows developers to easily support editing of a value on any page. The interface is used in places such as the course section and activity name editing.

inplace editable example.png

Implementing inplace_editable in a plugin

The best way is to explain the usage on a simple example. Imagine we have plugin tool_mytest that needs to implement in-place editing of a field 'name' from db table tool_mytest_mytable. We are going to call this itemtype mytestname. Each plugin (or core component) may use as many item types as it needs.

Define a callback in /admin/tool/mytest/lib.php that starts with the plugin name and ends with _inplace_editable:

function tool_mytest_inplace_editable($itemtype, $itemid, $newvalue) {
global $DB;

if ($itemtype === 'mytestname') {
$record = $DB->get_record('tool_mytest_mytable', ['id' => $itemid], '*', MUST_EXIST);

// Must call validate_context for either system, or course or course module context.
// This will both check access and set current context.

// Check permission of the user to update this item.
require_capability('tool/mytest:update', context_system::instance());

// Clean input and update the record.
$newvalue = clean_param($newvalue, PARAM_NOTAGS);

$DB->update_record('tool_mytest_mytable', ['id' => $itemid, 'name' => $newvalue));

// Prepare the element for the output:
$record->name = $newvalue;

return new \core\output\inplace_editable(
get_string('editmytestnamefield', 'tool_mytest'),
get_string('newvaluestring', 'tool_mytest', format_string($record->name))

In your renderer or wherever you actually display the name, use the same inplace_editable template:

$tmpl = new \core\output\inplace_editable(
has_capability('tool/mytest:update', context_system::instance()),
new lang_string('editmytestnamefield', 'tool_mytest'),
new lang_string('newvaluestring', 'tool_mytest', format_string($record->name))
echo $OUTPUT->render($tmpl);

This was a very simplified example, in the real life you will probably want to:

  • Create a function (or class extending core\output\inplace_editable) to form the instance of templatable object so you don't need to duplicate code;
  • Use an existing function to update a record (which hopefully also validates input value and triggers events)
  • Add unit tests and behat tests

Toggles and dropdowns

You may choose to set the UI for your inplace editable element to be a string value (default), toggle or dropdown.

Examples of dropdown setup (see also example by overriding class):

$tagcollections = \core_tag_collection::get_collections_menu(true);
$tmpl = new \core\output\inplace_editable(

// Note that $displayvalue is not needed (null was passed in the example above).
// It will be automatically taken from options.

// $value must be an existing index from the $tagcollections array,
// otherwise exception will be thrown.

Example of toggle setup (see also example by overriding class):

$tmpl = new \core\output\inplace_editable(




// $displayvalue usually toggles an image, for example closed/open eye.
// It is easier to implement by overriding the class.
// In this case $displayvalue can be generated from $value during exporting.

// $value must be an existing element of the array
// passed to set_type_toggle(), otherwise exception will be thrown.

$tmpl->set_type_toggle([0, 1]);

How does it work

inplace_editable consists of

  • Templatable/renderable class core\output\inplace_editable
  • Template core/inplace_editable
  • JavaScript module core/inplace_editable
  • Web service core_update_inplace_editable available from AJAX

All four call each other so it's hard to decide where we start explaining this circle of friends but let's start with web service.

  1. Web service receives arguments ($component, $itemtype, $itemid, $newvalue) - it searches for the inplace_editable callback in the component. Then web service calls this callback as {component}_inplace_editable($itemtype, $itemid, $newvalue), this must return templatable element which is sent back to the web service caller. Web service requires user to be logged in. Any other capability/access checks must be performed inside the callback.

  2. Templatable element contains such properties as component, itemtype, itemid, displayvalue, value, editlabel and edithint. When used in a template It only renders the display value and the edit link (with title=edithint). All other properties are rendered as data-xxx attributes. Template also ensures that JavaScript module is loaded.

  3. JavaScript module registers a listener to when the edit link is clicked and then it replaces the display value with the text input box that allows to edit value. When user presses "Enter" the AJAX request is called to the web service and code from the component is executed. If web service throws an exception it is displayed for user as a popup.


Plugin page can listen to JQuery events that are triggered on successful update or when update failed. Example of the listeners (as inline JS code):

require(['jquery'], function(\$) {
$('body').on('updatefailed', '[data-inplaceeditable]', (e) => {
// The exception object returned by the callback.
const exception = e.exception;

// The value that user tried to udpated the element to.
const newvalue = e.newvalue;

// This will prevent default error dialogue.

// Do your own error processing here.
$('body').on('updated', '[data-inplaceeditable]', (e) => {
// Everything that web service returned.
const ajaxreturn = e.ajaxreturn;

// Element value before editing (note, this is raw value and not display value).
const oldvalue = e.oldvalue;

// Do your own stuff, for example update all other occurences of this element on the page.

The above examples are not recommended and just give an example of how these APIs work.