5 ### What can I do with plugins?
7 The plugin system lets you:
9 - insert content into specific places across templates.
10 - alter data before templates rendering.
11 - alter data before saving new links.
14 ### How can I create a plugin for Shaarli?
16 First, chose a plugin name, such as `demo_plugin`.
18 Under `plugin` folder, create a folder named with your plugin name. Then create a <plugin_name>.meta file and a <plugin_name>.php file in that folder.
20 You should have the following tree view:
26 | |---| demo_plugin.meta
27 | |---| demo_plugin.php
31 ### Plugin initialization
33 At the beginning of Shaarli execution, all enabled plugins are loaded. At this point, the plugin system looks for an `init()` function in the <plugin_name>.php to execute and run it if it exists. This function must be named this way, and takes the `ConfigManager` as parameter.
35 <plugin_name>_init($conf)
37 This function can be used to create initial data, load default settings, etc. But also to set *plugin errors*. If the initialization function returns an array of strings, they will be understand as errors, and displayed in the header to logged in users.
39 The plugin system also looks for a `description` variable in the <plugin_name>.meta file, to be displayed in the plugin administration page.
41 description="The plugin does this and that."
43 ### Understanding hooks
45 A plugin is a set of functions. Each function will be triggered by the plugin system at certain point in Shaarli execution.
47 These functions need to be named with this pattern:
50 hook_<plugin_name>_<hook_name>($data, $conf)
55 - data: see [$data section](https://shaarli.readthedocs.io/en/master/Plugin-System/#plugins-data)
56 - conf: the `ConfigManager` instance.
58 For example, if my plugin want to add data to the header, this function is needed:
60 hook_demo_plugin_render_header
62 If this function is declared, and the plugin enabled, it will be called every time Shaarli is rendering the header.
69 Every hook function has a `$data` parameter. Its content differs for each hooks.
71 **This parameter needs to be returned every time**, otherwise data is lost.
77 Special additional data are passed to every hook through the
78 `$data` parameter to give you access to additional context, and services.
82 * `_PAGE_` (string): if the current hook is used to render a template, its name is passed through this additional parameter.
83 * `_LOGGEDIN_` (bool): whether the user is logged in or not.
84 * `_BASE_PATH_` (string): if Shaarli instance is hosted under a subfolder, contains the subfolder path to `index.php` (e.g. `https://domain.tld/shaarli/` -> `/shaarli/`).
85 * `_BOOKMARK_SERVICE_` (`BookmarkServiceInterface`): bookmark service instance, for advanced usage.
90 if ($data['_PAGE_'] === TemplatePage::LINKLIST && $data['LOGGEDIN'] === true) {
91 // Do something for logged in users when the link list is rendered
95 #### Filling templates placeholder
97 Template placeholders are displayed in template in specific places.
99 RainTPL displays every element contained in the placeholder's array. These element can be added by plugins.
101 For example, let's add a value in the placeholder `top_placeholder` which is displayed at the top of my page:
104 $data['top_placeholder'][] = 'My content';
106 array_push($data['top_placeholder'], 'My', 'content');
112 #### Data manipulation
114 When a page is displayed, every variable send to the template engine is passed to plugins before that in `$data`.
116 The data contained by this array can be altered before template rendering.
118 For example, in linklist, it is possible to alter every title:
121 // mind the reference if you want $data to be altered
122 foreach ($data['links'] as &$value) {
123 // String reverse every title.
124 $value['title'] = strrev($value['title']);
132 Every plugin needs a `<plugin_name>.meta` file, which is in fact an `.ini` file (`KEY="VALUE"`), to be listed in plugin administration.
134 Each file contain two keys:
136 - `description`: plugin description
137 - `parameters`: user parameter names, separated by a `;`.
138 - `parameter.<PARAMETER_NAME>`: add a text description the specified parameter.
140 > Note: In PHP, `parse_ini_file()` seems to want strings to be between by quotes `"` in the ini file.
142 ### Register plugin's routes
144 Shaarli lets you register custom Slim routes for your plugin.
146 To register a route, the plugin must include a function called `function <plugin_name>_register_routes(): array`.
148 This method must return an array of routes, each entry must contain the following keys:
150 - `method`: HTTP method, `GET/POST/PUT/PATCH/DELETE`
151 - `route` (path): without prefix, e.g. `/up/{variable}`
152 It will be later prefixed by `/plugin/<plugin name>/`.
153 - `callable` string, function name or FQN class's method to execute, e.g. `demo_plugin_custom_controller`.
155 Callable functions or methods must have `Slim\Http\Request` and `Slim\Http\Response` parameters
156 and return a `Slim\Http\Response`. We recommend creating a dedicated class and extend either
157 `ShaarliVisitorController` or `ShaarliAdminController` to use helper functions they provide.
159 A dedicated plugin template is available for rendering content: `pluginscontent.html` using `content` placeholder.
161 > **Warning**: plugins are not able to use RainTPL template engine for their content due to technical restrictions.
162 > RainTPL does not allow to register multiple template folders, so all HTML rendering must be done within plugin
165 Check out the `demo_plugin` for a live example: `GET <shaarli_url>/plugin/demo_plugin/custom`.
167 ### Understanding relative paths
169 Because Shaarli is a self-hosted tool, an instance can either be installed at the root directory, or under a subfolder.
170 This means that you can *never* use absolute paths (eg `/plugins/mything/file.png`).
172 If a file needs to be included in server end, use simple relative path:
173 `PluginManager::$PLUGINS_PATH . '/mything/template.html'`.
175 If it needs to be included in front end side (e.g. an image),
176 the relative path must be prefixed with special data:
178 * if it's a link that will need to be processed by Shaarli, use `_BASE_PATH_`:
179 for e.g. `$data['_BASE_PATH_'] . '/admin/tools`.
180 * if you want to include an asset, you need to add the root URL (base path without `/index.php`, for people using Shaarli without URL rewriting), then use `_ROOT_PATH_`:
182 `$['_ROOT_PATH_'] . '/' . PluginManager::$PLUGINS_PATH . '/mything/picture.png`.
184 Note that special placeholders for CSS and JS files (respectively `css_files` and `js_files`) are already prefixed
185 with the root path in template files.
187 ### It's not working!
189 Use `demo_plugin` as a functional example. It covers most of the plugin system features.
191 If it's still not working, please [open an issue](https://github.com/shaarli/Shaarli/issues/new).
196 | Hooks | Description |
197 | ------------- |:-------------:|
198 | [render_header](#render_header) | Allow plugin to add content in page headers. |
199 | [render_includes](#render_includes) | Allow plugin to include their own CSS files. |
200 | [render_footer](#render_footer) | Allow plugin to add content in page footer and include their own JS files. |
201 | [render_linklist](#render_linklist) | It allows to add content at the begining and end of the page, after every link displayed and to alter link data. |
202 | [render_editlink](#render_editlink) | Allow to add fields in the form, or display elements. |
203 | [render_tools](#render_tools) | Allow to add content at the end of the page. |
204 | [render_picwall](#render_picwall) | Allow to add content at the top and bottom of the page. |
205 | [render_tagcloud](#render_tagcloud) | Allow to add content at the top and bottom of the page, and after all tags. |
206 | [render_taglist](#render_taglist) | Allow to add content at the top and bottom of the page, and after all tags. |
207 | [render_daily](#render_daily) | Allow to add content at the top and bottom of the page, the bottom of each link and to alter data. |
208 | [render_feed](#render_feed) | Allow to do add tags in RSS and ATOM feeds. |
209 | [save_link](#save_link) | Allow to alter the link being saved in the datastore. |
210 | [delete_link](#delete_link) | Allow to do an action before a link is deleted from the datastore. |
211 | [save_plugin_parameters](#save_plugin_parameters) | Allow to manipulate plugin parameters before they're saved. |
216 Triggered on every page - allows plugins to add content in page headers.
221 `$data` is an array containing:
223 - [Special data](#special-data)
225 ##### Template placeholders
227 Items can be displayed in templates by adding an entry in `$data['<placeholder>']` array.
229 List of placeholders:
231 - `buttons_toolbar`: after the list of buttons in the header.
233 ![buttons_toolbar_example](http://i.imgur.com/ssJUOrt.png)
235 - `fields_toolbar`: after search fields in the header.
237 > Note: This will only be called in linklist.
239 ![fields_toolbar_example](http://i.imgur.com/3GMifI2.png)
244 Triggered on every page - allows plugins to include their own CSS files.
248 `$data` is an array containing:
250 - [Special data](#special-data)
252 ##### Template placeholders
254 Items can be displayed in templates by adding an entry in `$data['<placeholder>']` array.
256 List of placeholders:
258 - `css_files`: called after loading default CSS.
260 > Note: only add the path of the CSS file. E.g: `plugins/demo_plugin/custom_demo.css`.
265 Triggered on every page.
267 Allow plugin to add content in page footer and include their own JS files.
271 `$data` is an array containing:
273 - [Special data](#special-data)
275 ##### Template placeholders
277 Items can be displayed in templates by adding an entry in `$data['<placeholder>']` array.
279 List of placeholders:
281 - `text`: called after the end of the footer text.
282 - `endofpage`: called at the end of the page.
284 ![text_example](http://i.imgur.com/L5S2YEH.png)
286 - `js_files`: called at the end of the page, to include custom JS scripts.
288 > Note: only add the path of the JS file. E.g: `plugins/demo_plugin/custom_demo.js`.
293 Triggered when `linklist` is displayed (list of links, permalink, search, tag filtered, etc.).
295 It allows to add content at the begining and end of the page, after every link displayed and to alter link data.
299 `$data` is an array containing:
301 - All templates data, including links.
302 - [Special data](#special-data)
304 ##### template placeholders
306 Items can be displayed in templates by adding an entry in `$data['<placeholder>']` array.
308 List of placeholders:
310 - `action_plugin`: next to the button "private only" at the top and bottom of the page.
312 ![action_plugin_example](http://i.imgur.com/Q12PWg0.png)
314 - `link_plugin`: for every link, between permalink and link URL.
316 ![link_plugin_example](http://i.imgur.com/3oDPhWx.png)
318 - `plugin_start_zone`: before displaying the template content.
320 ![plugin_start_zone_example](http://i.imgur.com/OVBkGy3.png)
322 - `plugin_end_zone`: after displaying the template content.
324 ![plugin_end_zone_example](http://i.imgur.com/6IoRuop.png)
329 Triggered when the link edition form is displayed.
331 Allow to add fields in the form, or display elements.
335 `$data` is an array containing:
337 - All templates data.
338 - [Special data](#special-data)
340 ##### template placeholders
342 Items can be displayed in templates by adding an entry in `$data['<placeholder>']` array.
344 List of placeholders:
346 - `edit_link_plugin`: after tags field.
348 ![edit_link_plugin_example](http://i.imgur.com/5u17Ens.png)
353 Triggered when the "tools" page is displayed.
355 Allow to add content at the end of the page.
359 `$data` is an array containing:
361 - All templates data.
362 - [Special data](#special-data)
364 ##### template placeholders
366 Items can be displayed in templates by adding an entry in `$data['<placeholder>']` array.
368 List of placeholders:
370 - `tools_plugin`: at the end of the page.
372 ![tools_plugin_example](http://i.imgur.com/Bqhu9oQ.png)
377 Triggered when picwall is displayed.
379 Allow to add content at the top and bottom of the page.
383 `$data` is an array containing:
385 - All templates data.
386 - [Special data](#special-data)
388 ##### template placeholders
390 Items can be displayed in templates by adding an entry in `$data['<placeholder>']` array.
392 List of placeholders:
394 - `plugin_start_zone`: before displaying the template content.
395 - `plugin_end_zone`: after displaying the template content.
397 ![plugin_start_end_zone_example](http://i.imgur.com/tVTQFER.png)
402 Triggered when tagcloud is displayed.
404 Allow to add content at the top and bottom of the page.
408 `$data` is an array containing:
410 - All templates data.
411 - [Special data](#special-data)
413 ##### Template placeholders
415 Items can be displayed in templates by adding an entry in `$data['<placeholder>']` array.
417 List of placeholders:
419 - `plugin_start_zone`: before displaying the template content.
420 - `plugin_end_zone`: after displaying the template content.
422 For each tag, the following placeholder can be used:
424 - `tag_plugin`: after each tag
426 ![plugin_start_end_zone_example](http://i.imgur.com/vHmyT3a.png)
431 Triggered when taglist is displayed - allows to add content at the top and bottom of the page.
435 `$data` is an array containing:
437 - All templates data.
438 - [Special data](#special-data)
440 ##### Template placeholders
442 Items can be displayed in templates by adding an entry in `$data['<placeholder>']` array.
444 List of placeholders:
446 - `plugin_start_zone`: before displaying the template content.
447 - `plugin_end_zone`: after displaying the template content.
449 For each tag, the following placeholder can be used:
451 - `tag_plugin`: after each tag
455 Triggered when tagcloud is displayed.
457 Allow to add content at the top and bottom of the page, the bottom of each link and to alter data.
462 `$data` is an array containing:
464 - All templates data, including links.
465 - [Special data](#special-data)
467 ##### Template placeholders
469 Items can be displayed in templates by adding an entry in `$data['<placeholder>']` array.
471 List of placeholders:
473 - `link_plugin`: used at bottom of each link.
475 ![link_plugin_example](http://i.imgur.com/hzhMfSZ.png)
477 - `plugin_start_zone`: before displaying the template content.
478 - `plugin_end_zone`: after displaying the template content.
483 Triggered when the ATOM or RSS feed is displayed.
485 Allow to add tags in the feed, either in the header or for each items. Items (links) can also be altered before being rendered.
489 `$data` is an array containing:
491 - All templates data, including links.
492 - [Special data](#special-data)
494 ##### Template placeholders
496 Tags can be added in feeds by adding an entry in `$data['<placeholder>']` array.
498 List of placeholders:
500 - `feed_plugins_header`: used as a header tag in the feed.
504 - `feed_plugins`: additional tag for every link entry.
509 Triggered when a link is save (new link or edit).
511 Allow to alter the link being saved in the datastore.
515 `$data` is an array containing the link being saved:
527 Also [special data](#special-data).
532 Triggered when a link is deleted.
534 Allow to execute any action before the link is actually removed from the datastore
538 `$data` is an array containing the link being deleted:
550 Also [special data](#special-data).
552 #### save_plugin_parameters
554 Triggered when the plugin parameters are saved from the plugin administration page.
556 Plugins can perform an action every times their settings are updated.
557 For example it is used to update the CSS file of the `default_colors` plugins.
561 `$data` input contains the `$_POST` array.
563 So if the plugin has a parameter called `MYPLUGIN_PARAMETER`,
564 the array will contain an entry with `MYPLUGIN_PARAMETER` as a key.
566 Also [special data](#special-data).
568 ## Guide for template designers
570 ### Plugin administration
572 Your theme must include a plugin administration page: `pluginsadmin.html`.
574 > Note: repo's template link needs to be added when the PR is merged.
576 Use the default one as an example.
578 Aside from classic RainTPL loops, plugins order is handle by JavaScript. You can just include `plugin_admin.js`, only if:
580 - you're using a table.
581 - you call orderUp() and orderUp() onclick on arrows.
582 - you add data-line and data-order to your rows.
584 Otherwise, you can use your own JS as long as this field is send by the form:
586 <input type="hidden" name="order_{$key}" value="{$counter}">
588 ### Placeholder system
590 In order to make plugins work with every custom themes, you need to add variable placeholder in your templates.
592 It's a RainTPL loop like this:
594 {loop="$plugin_variable"}
598 You should enable `demo_plugin` for testing purpose, since it uses every placeholder available.
600 ### List of placeholders
604 At the end of the menu:
606 {loop="$plugins_header.buttons_toolbar"}
610 At the end of file, before clearing floating blocks:
612 {if="!empty($plugin_errors) && $is_logged_in"}
614 {loop="plugin_errors"}
622 At the end of the file:
625 {loop="$plugins_includes.css_files"}
626 <link type="text/css" rel="stylesheet" href="{$value}#"/>
632 At the end of your footer notes:
635 {loop="$plugins_footer.text"}
643 {loop="$plugins_footer.js_files"}
644 <script src="{$value}#"></script>
653 {loop="$plugins_header.fields_toolbar"}
658 Before displaying the link list (after paging):
661 {loop="$plugin_start_zone"}
666 For every links (icons):
669 {loop="$value.link_plugin"}
670 <span>{$value}</span>
677 {loop="$plugin_end_zone"}
682 **linklist.paging.html**
684 After the "private only" icon:
687 {loop="$action_plugin"}
697 {loop="$edit_link_plugin"}
707 {loop="$tools_plugin"}
717 <div id="plugin_zone_start_picwall" class="plugin_zone">
718 {loop="$plugin_start_zone"}
727 <div id="plugin_zone_end_picwall" class="plugin_zone">
728 {loop="$plugin_end_zone"}
739 <div id="plugin_zone_start_tagcloud" class="plugin_zone">
740 {loop="$plugin_start_zone"}
749 <div id="plugin_zone_end_tagcloud" class="plugin_zone">
750 {loop="$plugin_end_zone"}
761 <div id="plugin_zone_start_picwall" class="plugin_zone">
762 {loop="$plugin_start_zone"}
771 <div class="dailyEntryFooter">
772 {loop="$link.link_plugin"}
781 <div id="plugin_zone_end_picwall" class="plugin_zone">
782 {loop="$plugin_end_zone"}
788 **feed.atom.xml** and **feed.rss.xml**:
790 In headers tags section:
792 {loop="$feed_plugins_header"}
799 {loop="$value.feed_plugins"}