OK, here is a list of suggestions I have collected so far:
- Remove SED_EXTPLUGIN block from every single plugin file. In fact, it is more annoying and redundant rather than useful. "Code" is the same as plugin name. "Part" can be identified by file name. "Hooks" can be binded in setup file (see below). "Tags" are better to be collected they way "tpltags" plugin does it (by scanning the code instead of forcing plugin developer to describe every tag). "Order" can be specified in hook binding.
- Specify hook bindings as an array in setup file like:
$hooks = array(
array('filename1', 'hook1', 10),
array('filename1', 'hook2'),
array('filename2', 'hook3', 99)
);
- Automatically preload plugin permissions into $usr['auth_read'], $usr['auth_write'] and $usr['isadmin'].
- Automatically preload plugin langfile.
- Already added in tickets: simplify CODE check. It can be
defined('COT_CODE') or die('Wrong URL');
- Time to change sed_ to cot_
More brainstorming while writing a plugin:
7.
Auth hooks. Add ability to affect auth in exact places (already known as EYOOP issue).
8.
SQL query hooks. There are some important queries that a plugin developer would like to modify before they get executed. For example, if you want to affect forum posts order and join it with another table. Currently queries are executed like $sql = sed_sql_query("SELECT ..."), so the only way to change it is either a corehack or another similar query. If we did it like:
$query = "SELECT ...";
forums_posts_query(); // HOOK here
$sql = cot_query($query);
it could leave a possibility to edit the query with a plugin before it gets executed. It's not the most elegant way to modify a query, but if you know a better way, don't hesitate to share.
