Skip to content

Latest commit

 

History

History
49 lines (35 loc) · 1.56 KB

cp-section.md

File metadata and controls

49 lines (35 loc) · 1.56 KB

Control Panel Section

Plugins can provide their own section in the Control Panel by adding a hasCpSection property to their plugin:

<?php

namespace ns\prefix;

class Plugin extends \craft\base\Plugin
{
    public $hasCpSection = true;

    // ...
}

With that in place, Craft will add a new user permission for your plugin, and users that have it will get a new item in their global Control Panel nav, pointing to /admin/plugin-handle.

{tip} That plugin-handle segment is your plugin handle, converted from camelCase to kebab-case.

By default, when someone goes to /admin/plugin-handle, Craft will look for an index.html or index.twig template within your plugin’s templates/ directory (which should go in your plugin’s source directory).

At a minimum, that template should extend Craft’s _layouts/cp layout template, set a title variable, and override the content block.

{% extends "_layouts/cp" %}
{% set title = "Page Title"|t('app') %}

{% block content %}
    <p>Page content goes here</p>
{% endblock %}

Alternatively, you can route requests to /admin/plugin-handle to a controller action (or a different template) by registering a Control Panel route from your plugin’s init() method:

use craft\events\RegisterUrlRulesEvent;
use craft\web\UrlManager;
use yii\base\Event;

public function init()
{
    Event::on(UrlManager::class, UrlManager::EVENT_REGISTER_CP_URL_RULES, function(RegisterUrlRulesEvent $event) {
        $event->rules['plugin-handle'] = 'plugin-handle/foo/bar';
    });
}