Fixes #378 - Plugin administration UI.

[ArthurHoaro]

Features

From the administration panel, users can:

• See all plugin name and description available.
• Enable/disable plugins.
• Change loading order of their plugins (affects for example shaares icon order).
• Affect and change plugins parameters.

Plugin developer side

Every plugin needs a <plugin_name>.meta file which is in fact an .ini file (KEY="VALUE") to be listed in plugin administration.

Each file contain two keys:

• description: plugin description
• parameters: user parameter names, separated by a ;.

Note: In PHP, parse_ini_file() seems to want strings to be between by quotes " in the ini file.

Theme maintainers

There is a new page: pluginsadmin.html. It needs to be added to your theme. I'll update documentation later.

Aside from classic RainTPL loops, plugins order is handle by JavaScript. You can use plugin_admin.js, only if:

• you're using a table.
• you call orderUp() and orderUp() onclick on arrows.
• you add data-line and data-order to your rows.

Otherwise, theme maintainers can use their own JS as long as this field is send by the form:

<input type="hidden" name="order_{$key}" value="{$counter}">

Other

• In tools.html, moved "Change password" after Shaarli and plugins configuration.
• Unit tests.
• 2 new page in Router: pluginadmin and save_pluginadmin.

Preview

TODO

• Documentation!

[virtualtam]

Neat \o/

Gonna start to test it during the upcoming weekend!

[ArthurHoaro]

Rebased.

[virtualtam]

though 4 spaces are a common indentation value for most languages, HTML devs tend to stick to using 2 spaces to keep the overall code readable:

• w3schools recommendation
• Google HTML/CSS guide

[ArthurHoaro]

That's better!

[virtualtam]

First batch of comments posted ;-)

[ArthurHoaro]

Thanks for the review! I had miss a few things! ;)
This one is still open.

[ArthurHoaro]

Documentation updated:

• user guide
• meta
• template

[ArthurHoaro]

I just force pushed an outdated version. -.-
I'll re-fix your review and merge.