Please see the sample addon 'randplace' for a working example of using some of these features. Addons work by intercepting event hooks - which must be registered. Modules work by intercepting specific page requests (by URL path).
Addon names cannot contain spaces or other punctuation and are used as filenames and function names. You may supply a "friendly" name within the comment block. Each addon must contain both an install and an uninstall function based on the addon name. For instance "addon1name_install()". These two functions take no arguments and are usually responsible for registering (and unregistering) event hooks that your addon will require. The install and uninstall functions will also be called (i.e. re-installed) if the addon changes after installation. Therefore your uninstall should not destroy data and install should consider that data may already exist. Future extensions may provide for "setup" amd "remove".
Addons should contain a comment block with the four following parameters:
/*
* Name: My Great Addon
* Description: This is what my addon does. It's really cool.
* Version: 1.0
* Author: John Q. Public <john@myfriendicasite.com>
*/
Please also add a README or README.md file to the addon directory. It will be displayed in the admin panel and should include some further information in addition to the header information.
Register your addon hooks during installation.
\Friendica\Core\Hook::register($hookname, $file, $function);
$hookname is a string and corresponds to a known Friendica PHP hook.
$file is a pathname relative to the top-level Friendica directory. This should be 'addon/addon_name/addon_name.php' in most cases.
$function is a string and is the name of the function which will be executed when the hook is called.
Your hook callback functions will be called with at least one and possibly two arguments
function myhook_function(App $a, &$b) {
}
If you wish to make changes to the calling data, you must declare them as reference variables (with &
) during function declaration.
$a is the Friendica App
class.
It contains a wealth of information about the current state of Friendica:
It is recommeded you call this $a
to match its usage elsewhere.
$b can be called anything you like.
This is information specific to the hook currently being processed, and generally contains information that is being immediately processed or acted on that you can use, display, or alter.
Remember to declare it with &
if you wish to alter it.
If your addon requires adding a stylesheet on all pages of Friendica, add the following hook:
function <addon>_install()
{
\Friendica\Core\Hook::register('head', __FILE__, '<addon>_head');
...
}
function <addon>_head(App $a)
{
$a->registerStylesheet(__DIR__ . '/relative/path/to/addon/stylesheet.css');
}
__DIR__
is the folder path of your addon.
If your addon requires adding a script on all pages of Friendica, add the following hook:
function <addon>_install()
{
\Friendica\Core\Hook::register('footer', __FILE__, '<addon>_footer');
...
}
function <addon>_footer(App $a)
{
$a->registerFooterScript(__DIR__ . '/relative/path/to/addon/script.js');
}
__DIR__
is the folder path of your addon.
The main Friendica script provides hooks via events dispatched on the document
property.
In your Javascript file included as described above, add your event listener like this:
document.addEventListener(name, callback);
More info about Javascript event listeners: https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener
Called at the end of the live update process (XmlHttpRequest) and on a post preview. No additional data is provided.
Addons may also act as "modules" and intercept all page requests for a given URL path. In order for a addon to act as a module it needs to define a function "addon_name_module()" which takes no arguments and needs not do anything.
If this function exists, you will now receive all page requests for "http://my.web.site/addon_name" - with any number of URL components as additional arguments. These are parsed into an array $a->argv, with a corresponding $a->argc indicating the number of URL components. So http://my.web.site/addon/arg1/arg2 would look for a module named "addon" and pass its module functions the $a App structure (which is available to many components). This will include:
$a->argc = 3
$a->argv = array(0 => 'addon', 1 => 'arg1', 2 => 'arg2');
Your module functions will often contain the function addon_name_content(App $a), which defines and returns the page body content. They may also contain addon_name_post(App $a) which is called before the _content function and typically handles the results of POST forms. You may also have addon_name_init(App $a) which is called very early on and often does module initialisation.
If your addon needs some template, you can use the Friendica template system. Friendica uses smarty3 as a template engine.
Put your tpl files in the templates/ subfolder of your addon.
In your code, like in the function addon_name_content(), load the template file and execute it passing needed values:
# load template file. first argument is the template name,
# second is the addon path relative to friendica top folder
$tpl = Renderer::getMarkupTemplate('mytemplate.tpl', 'addon/addon_name/');
# apply template. first argument is the loaded template,
# second an array of 'name' => 'values' to pass to template
$output = Renderer::replaceMacros($tpl, array(
'title' => 'My beautiful addon',
));
See also the wiki page Quick Template Guide.
Called when a user attempts to login.
$b
is an array containing:
Called after a user has successfully logged in.
$b
contains the $a->user
array.
Called when formatting a post for display. $b is an array:
Called when a status post or comment is entered on the local system.
$b
is the item array of the information to be stored in the database.
Please note: body contents are bbcode - not HTML.
Called when a local status post or comment has been stored on the local system.
$b
is the item array of the information which has just been stored in the database.
Please note: body contents are bbcode - not HTML
Called when receiving a post from another source. This may also be used to post local activity or system generated messages.
$b
is the item array of information to be stored in the database and the item body is bbcode.
Called when generating the HTML for the user Settings page.
$b
is the HTML string of the settings page before the final </form>
tag.
Called when the Settings pages are submitted.
$b
is the $_POST array.
Called when generating the HTML for the addon settings page.
$b
is the (string) HTML of the addon settings page before the final </form>
tag.
Called when the Addon Settings pages are submitted.
$b
is the $_POST array.
Called when posting a profile page.
$b
is the $_POST array.
Called prior to output of profile edit page.
$b
is an array containing:
Called when the HTML is generated for the Advanced profile, corresponding to the Profile tab within a person's profile page.
$b
is the HTML string representation of the generated profile.
The profile array details are in $a->profile
.
Called from the Directory page when formatting an item for display.
$b
is an array:
Called prior to generating the sidebar "short" profile for a page.
$b
is the person's profile array
Called when generating the sidebar "short" profile for a page.
$b
is an array:
Called when formatting the block of contacts/friends on a profile sidebar has completed.
$b
is an array:
Called after conversion of bbcode to HTML.
$b
is an HTML string converted text.
Called after tag conversion of HTML to bbcode (e.g. remote message posting)
$b
is a string converted text
Called when building the <head>
sections.
Stylesheets should be registered using this hook.
$b
is an HTML string of the <head>
tag.
Called after building the page navigation section.
$b
is a string HTML of nav region.
Called prior to output of personal XRD file.
$b
is an array:
Called prior to output home page content, shown to unlogged users.
$b
is the HTML sring of section region.
Called when editing contact details on an individual from the Contacts page. $b is an array:
Called when posting the contact edit page.
$b
is the $_POST
array
Called just after DB has been opened and before session start. No hook data.
Called after HTML content functions have completed.
$b
is (string) HTML of content div.
Called after HTML content functions have completed.
Deferred Javascript files should be registered using this hook.
$b
is (string) HTML of footer div/element.
Called when looking up the avatar. $b
is an array:
Called from Emailer::send()
before building the mime message.
$b
is an array of params to Emailer::send()
.
Called before calling PHP's mail()
.
$b
is an array of params to mail()
.
Called during App
initialization to allow addons to load their own configuration file(s) with App::loadConfigFile()
.
Called after the navigational menu is build in include/nav.php
.
$b
is an array containing $nav
from include/nav.php
.
Called before vars are passed to the template engine to render the page.
The registered function can add,change or remove variables passed to template.
$b
is an array with:
Called after the other queries have passed.
The registered function can add, change or remove the acl_lookup()
variables.
Called at the start of prepare_body Hook data:
Called before the HTML conversion in prepare_body. If the item matches a content filter rule set by an addon, it should just add the reason to the filter_reasons element of the hook data. Hook data:
Called after the HTML conversion in prepare_body()
.
Hook data:
Called at the end of prepare_body()
.
Hook data:
Called after prepare_text()
in put_item_in_cache()
.
Hook data:
Called when a magic-auth was successful. Hook data:
visitor => array with the contact record of the visitor
url => the query string
Here is a complete list of all hook callbacks with file locations (as of 24-Sep-2018). Please see the source for details of any hooks not documented above.
Hook::callAll('init_1');
Hook::callAll('app_menu', $arr);
Hook::callAll('page_content_top', $a->page['content']);
Hook::callAll($a->module.'_mod_init', $placeholder);
Hook::callAll($a->module.'_mod_init', $placeholder);
Hook::callAll($a->module.'_mod_post', $_POST);
Hook::callAll($a->module.'_mod_afterpost', $placeholder);
Hook::callAll($a->module.'_mod_content', $arr);
Hook::callAll($a->module.'_mod_aftercontent', $arr);
Hook::callAll('page_end', $a->page['content']);
Hook::callAll('logged_in', $a->user);
Hook::callAll('authenticate', $addon_auth);
Hook::callAll('logged_in', $a->user);
Hook::callAll('enotify', $h);
Hook::callAll('enotify_store', $datarray);
Hook::callAll('enotify_mail', $datarray);
Hook::callAll('check_item_notification', $notification_data);
Hook::callAll('conversation_start', $cb);
Hook::callAll('render_location', $locate);
Hook::callAll('display_item', $arr);
Hook::callAll('display_item', $arr);
Hook::callAll('item_photo_menu', $args);
Hook::callAll('jot_tool', $jotplugins);
Hook::callAll('contact_block_end', $arr);
Hook::callAll('poke_verbs', $arr);
Hook::callAll('put_item_in_cache', $hook_data);
Hook::callAll('prepare_body_init', $item);
Hook::callAll('prepare_body_content_filter', $hook_data);
Hook::callAll('prepare_body', $hook_data);
Hook::callAll('prepare_body_final', $hook_data);
Hook::callAll('page_info_data', $data);
Hook::callAll('directory_item', $arr);
Hook::callAll('personal_xrd', $arr);
Hook::callAll('network_ping', $arr);
Hook::callAll("parse_link", $arr);
Hook::callAll('home_init', $ret);
Hook::callAll('acl_lookup_end', $results);
Hook::callAll('network_content_init', $arr);
Hook::callAll('network_tabs', $arr);
Hook::callAll('about_hook', $o);
Hook::callAll('post_local_end', $arr);
Hook::callAll('profile_post', $_POST);
Hook::callAll('profile_edit', $arr);
Hook::callAll('addon_settings_post', $_POST);
Hook::callAll('connector_settings_post', $_POST);
Hook::callAll('display_settings_post', $_POST);
Hook::callAll('settings_post', $_POST);
Hook::callAll('addon_settings', $settings_addons);
Hook::callAll('connector_settings', $settings_connectors);
Hook::callAll('display_settings', $o);
Hook::callAll('settings_form', $o);
Hook::callAll('photo_post_init', $_POST);
Hook::callAll('photo_post_file', $ret);
Hook::callAll('photo_post_end', $foo);
Hook::callAll('photo_post_end', $foo);
Hook::callAll('photo_post_end', $foo);
Hook::callAll('photo_post_end', $foo);
Hook::callAll('photo_post_end', intval($item_id));
Hook::callAll('photo_upload_form', $ret);
Hook::callAll('profile_advanced', $o);
Hook::callAll('home_init', $ret);
Hook::callAll("home_content", $content);
Hook::callAll('post_local_end', $arr);
Hook::callAll('contact_edit_post', $_POST);
Hook::callAll('contact_edit', $arr);
Hook::callAll('post_local_end', $arr);
Hook::callAll('lockview_content', $item);
Hook::callAll('uexport_options', $options);
Hook::callAll('register_post', $arr);
Hook::callAll('register_form', $arr);
Hook::callAll('post_local_start', $_REQUEST);
Hook::callAll('post_local', $datarray);
Hook::callAll('post_local_end', $datarray);
Hook::callAll('jot_tool', $jotplugins);
Hook::callAll('logged_in', $a->user);
Hook::callAll("template_vars", $arr);
Hook::callAll('load_config');
Hook::callAll('head');
Hook::callAll('footer');
Hook::callAll('post_local', $item);
Hook::callAll('post_remote', $item);
Hook::callAll('post_local_end', $posted_item);
Hook::callAll('post_remote_end', $posted_item);
Hook::callAll('tagged', $arr);
Hook::callAll('post_local_end', $new_item);
Hook::callAll('contact_photo_menu', $args);
Hook::callAll('follow', $arr);
Hook::callAll('profile_sidebar_enter', $profile);
Hook::callAll('profile_sidebar', $arr);
Hook::callAll('profile_tabs', $arr);
Hook::callAll('zrl_init', $arr);
Hook::callAll('magic_auth_success', $arr);
Hook::callAll('event_updated', $event['id']);
Hook::callAll("event_created", $event['id']);
Hook::callAll('register_account', $uid);
Hook::callAll('remove_user', $user);
Hook::callAll('bbcode', $text);
Hook::callAll('bb2diaspora', $text);
Hook::callAll('html2bbcode', $message);
Hook::callAll('smilie', $params);
Hook::callAll('isEnabled', $arr);
Hook::callAll('get', $arr);
Hook::callAll('network_to_name', $nets);
Hook::callAll('gender_selector', $select);
Hook::callAll('sexpref_selector', $select);
Hook::callAll('marital_selector', $select);
Hook::callAll('oembed_fetch_url', $embedurl, $j);
Hook::callAll('page_header', $a->page['nav']);
Hook::callAll('nav_info', $nav);
Hook::callAll('globaldir_update', $arr);
Hook::callAll('notifier_end', $target_item);
Hook::callAll('queue_predeliver', $r);
Hook::callAll('queue_deliver', $params);
Hook::callAll('authenticate', $addon_auth);
Hook::callAll('login_hook', $o);
Hook::callAll("logging_out");
Hook::callAll('render_location', $locate);
Hook::callAll('display_item', $arr);
Hook::callAll('contact_select_options', $x);
Hook::callAll($a->module.'_pre_'.$selname, $arr);
Hook::callAll($a->module.'_post_'.$selname, $o);
Hook::callAll($a->module.'_pre_'.$selname, $arr);
Hook::callAll($a->module.'_post_'.$selname, $o);
Hook::callAll('jot_networks', $jotnets);
Hook::callAll('logged_in', $a->user);
self::callSingle(self::getApp(), 'hook_fork', $fork_hook, $hookdata);
Hook::callAll("proc_run", $arr);
Hook::callAll('emailer_send_prepare', $params);
Hook::callAll("emailer_send", $hookdata);
Hook::callAll('generate_map', $arr);
Hook::callAll('generate_named_map', $arr);
Hook::callAll('Map::getCoordinates', $arr);
Hook::callAll('avatar_lookup', $avatar);
Hook::callAll("getsiteinfo", $siteinfo);
Hook::callAll('atom_feed_end', $atom);
Hook::callAll('atom_feed_end', $atom);
document.dispatchEvent(new Event('postprocess_liveupdate'));