MrPetovan/friendica
2
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

reformatted

Browse source
This commit is contained in:
Silke Meyer 2015-04-19 18:41:42 +02:00
parent ec584b164d
commit 7fdde0e547
1 changed files with 183 additions and 128 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

247
doc/Plugins.md
View file

@ -1,10 +1,19 @@
Friendica Addon/Plugin development Friendica Addon/Plugin development
========================== ==========================
Please see the sample addon 'randplace' for a working example of using some of these features. The facebook addon provides an example of integrating both "addon" and "module" functionality. Addons work by intercepting event hooks - which must be registered. Modules work by intercepting specific page requests (by URL path). Please see the sample addon 'randplace' for a working example of using some of these features.
The facebook addon provides an example of integrating both "addon" and "module" functionality.
Addons work by intercepting event hooks - which must be registered.
Modules work by intercepting specific page requests (by URL path).
Plugin names cannot contain spaces or other punctuation and are used as filenames and function names.
Plugin 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/plugin name. For instance "plugin1name_install()". These two functions take no arguments and are usually responsible for registering (and unregistering) event hooks that your plugin will require. The install and uninstall functions will also be called (i.e. re-installed) if the plugin 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". 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/plugin name.
For instance "plugin1name_install()".
These two functions take no arguments and are usually responsible for registering (and unregistering) event hooks that your plugin will require.
The install and uninstall functions will also be called (i.e. re-installed) if the plugin 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".
Plugins should contain a comment block with the four following parameters: Plugins should contain a comment block with the four following parameters:
@ -15,63 +24,71 @@ Plugins should contain a comment block with the four following parameters:
* Author: John Q. Public <john@myfriendicasite.com> * Author: John Q. Public <john@myfriendicasite.com>
*/ */
Register your plugin hooks during installation. Register your plugin hooks during installation.
register_hook($hookname, $file, $function); register_hook($hookname, $file, $function);
$hookname is a string and corresponds to a known Friendica hook. $hookname is a string and corresponds to a known Friendica hook.
$file is a pathname relative to the top-level Friendica directory. This *should* be 'addon/plugin_name/plugin_name.php' in most cases. $file is a pathname relative to the top-level Friendica directory.
This *should* be 'addon/plugin_name/plugin_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. $function is a string and is the name of the function which will be executed when the hook is called.
Arguments
---
Your hook callback functions will be called with at least one and possibly two arguments Your hook callback functions will be called with at least one and possibly two arguments
function myhook_function(&$a, &$b) { function myhook_function(&$a, &$b) {
} }
If you wish to make changes to the calling data, you must declare them as If you wish to make changes to the calling data, you must declare them as reference variables (with '&') during function declaration.
reference variables (with '&') during function declaration.
$a is the Friendica 'App' class - which contains a wealth of information ###$a
about the current state of Friendica, such as which module has been called, $a is the Friendica 'App' class.
configuration info, the page contents at the point the hook was invoked, profile It contains a wealth of information about the current state of Friendica:
and user information, etc. It is recommeded you call this '$a' to match its usage
elsewhere.
$b can be called anything you like. This is information which is specific to the hook * which module has been called,
currently being processed, and generally contains information that is being immediately * configuration information,
processed or acted on that you can use, display, or alter. Remember to declare it with * the page contents at the point the hook was invoked,
'&' if you wish to alter it. * profile and user information, etc.
It is recommeded you call this '$a' to match its usage elsewhere.
###$b
$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.
Modules Modules
-------- --------
Plugins/addons may also act as "modules" and intercept all page requests for a given URL path. In order for a plugin to act as a module it needs to define a function "plugin_name_module()" which takes no arguments and need not do anything. Plugins/addons may also act as "modules" and intercept all page requests for a given URL path.
In order for a plugin to act as a module it needs to define a function "plugin_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/plugin_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/plugin/arg1/arg2 would look for a module named "plugin" and pass its module functions the $a App structure (which is available to many components).
This will include:
If this function exists, you will now receive all page requests for "http://my.web.site/plugin_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/plugin/arg1/arg2 would look for a module named "plugin" and pass its module functions the $a App structure (which is available to many components). This will include:
$a->argc = 3 $a->argc = 3
$a->argv = array(0 => 'plugin', 1 => 'arg1', 2 => 'arg2'); $a->argv = array(0 => 'plugin', 1 => 'arg1', 2 => 'arg2');
Your module functions will often contain the function plugin_name_content(&$a), which defines and returns the page body content. They may also contain plugin_name_post(&$a) which is called before the _content function and typically handles the results of POST forms. You may also have plugin_name_init(&$a) which is called very early on and often does module initialisation. Your module functions will often contain the function plugin_name_content(&$a), which defines and returns the page body content.
They may also contain plugin_name_post(&$a) which is called before the _content function and typically handles the results of POST forms.
You may also have plugin_name_init(&$a) which is called very early on and often does module initialisation.
Templates Templates
---------- ----------
If your plugin need some template, you can use Friendica template system. Friendica use [smarty3](http://www.smarty.net/) as template engine. If your plugin needs some template, you can use the Friendica template system.
Friendica uses [smarty3](http://www.smarty.net/) as a template engine.
Put your tpl files in *templates/* subfolder of your plugin. Put your tpl files in the *templates/* subfolder of your plugin.
In your code, like in function plugin_name_content(), load template file and execute it passing needed values: In your code, like in the function plugin_name_content(), load the template file and execute it passing needed values:
# load template file. first argument is the template name, # load template file. first argument is the template name,
# second is the plugin path relative to friendica top folder # second is the plugin path relative to friendica top folder
@ -80,124 +97,159 @@ In your code, like in function plugin_name_content(), load template file and exe
# apply template. first argument is the loaded template, # apply template. first argument is the loaded template,
# second an array of 'name'=>'values' to pass to template # second an array of 'name'=>'values' to pass to template
$output = replace_macros($tpl,array( $output = replace_macros($tpl,array(
'title' => 'My beautifull plugin', 'title' => 'My beautiful plugin',
)); ));
See also wiki page [Quick Template Guide](https://github.com/friendica/friendica/wiki/Quick-Template-Guide) See also the wiki page [Quick Template Guide](https://github.com/friendica/friendica/wiki/Quick-Template-Guide).
Current hooks: Current hooks
-------------- -------------
###'authenticate'
'authenticate' is called when a user attempts to login.
$b is an array containing:
**'authenticate'** - called when a user attempts to login.
$b is an array
'username' => the supplied username 'username' => the supplied username
'password' => the supplied password 'password' => the supplied password
'authenticated' => set this to non-zero to authenticate the user. 'authenticated' => set this to non-zero to authenticate the user.
'user_record' => successful authentication must also return a valid user record from the database 'user_record' => successful authentication must also return a valid user record from the database
**'logged_in'** - called after a user has successfully logged in. ###'logged_in'
$b contains the $a->user array 'logged_in' is called after a user has successfully logged in.
$b contains the $a->user array.
###'display_item'
'display_item' is called when formatting a post for display.
$b is an array:
**'display_item'** - called when formatting a post for display.
$b is an array
'item' => The item (array) details pulled from the database 'item' => The item (array) details pulled from the database
'output' => the (string) HTML representation of this item prior to adding it to the page 'output' => the (string) HTML representation of this item prior to adding it to the page
**'post_local'** - called when a status post or comment is entered on the local system ###'post_local'
$b is the item array of the information to be stored in the database * called when a status post or comment is entered on the local system
{Please note: body contents are bbcode - not HTML) * $b is the item array of the information to be stored in the database
* Please note: body contents are bbcode - not HTML
**'post_local_end'** - called when a local status post or comment has been stored on the local system ###'post_local_end'
$b is the item array of the information which has just been stored in the database * called when a local status post or comment has been stored on the local system
{Please note: body contents are bbcode - not HTML) * $b is the item array of the information which has just been stored in the database
* Please note: body contents are bbcode - not HTML
**'post_remote'** - called when receiving a post from another source. This may also be used to post local activity or system generated messages. ###'post_remote'
$b is the item array of information to be stored in the database and the item * called when receiving a post from another source. This may also be used to post local activity or system generated messages.
body is bbcode. * $b is the item array of information to be stored in the database and the item body is bbcode.
**'settings_form'** - called when generating the HTML for the user Settings page ###'settings_form'
$b is the (string) HTML of the settings page before the final '</form>' tag. * called when generating the HTML for the user Settings page
* $b is the (string) HTML of the settings page before the final '</form>' tag.
**'settings_post'** - called when the Settings pages are submitted. ###'settings_post'
$b is the $_POST array * called when the Settings pages are submitted
* $b is the $_POST array
**'plugin_settings'** - called when generating the HTML for the addon settings page ###'plugin_settings'
$b is the (string) HTML of the addon settings page before the final '</form>' tag. * 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.
**'plugin_settings_post'** - called when the Addon Settings pages are submitted. ###'plugin_settings_post'
$b is the $_POST array * called when the Addon Settings pages are submitted
* $b is the $_POST array
**'profile_post'** - called when posting a profile page. ###'profile_post'
$b is the $_POST array * called when posting a profile page
* $b is the $_POST array
###'profile_edit'
'profile_edit' is called prior to output of profile edit page.
$b is an array containing:
**'profile_edit'** - called prior to output of profile edit page
$b is array
'profile' => profile (array) record from the database 'profile' => profile (array) record from the database
'entry' => the (string) HTML of the generated entry 'entry' => the (string) HTML of the generated entry
###'profile_advanced'
* called when the HTML is generated for the 'Advanced profile', corresponding to the 'Profile' tab within a person's profile page
* $b is the (string) HTML representation of the generated profile
* The profile array details are in $a->profile.
**'profile_advanced'** - called when the HTML is generated for the 'Advanced profile', corresponding to the 'Profile' tab within a person's profile page. ###'directory_item'
$b is the (string) HTML representation of the generated profile 'directory_item' is called from the Directory page when formatting an item for display.
(The profile array details are in $a->profile) $b is an array:
**'directory_item'** - called from the Directory page when formatting an item for display
$b is an array
'contact' => contact (array) record for the person from the database 'contact' => contact (array) record for the person from the database
'entry' => the (string) HTML of the generated entry 'entry' => the (string) HTML of the generated entry
**'profile_sidebar_enter'** - called prior to generating the sidebar "short" profile for a page ###'profile_sidebar_enter'
$b is (array) the person's profile array * called prior to generating the sidebar "short" profile for a page
* $b is the person's profile array
###'profile_sidebar'
'profile_sidebar is called when generating the sidebar "short" profile for a page.
$b is an array:
**'profile_sidebar'** - called when generating the sidebar "short" profile for a page
$b is an array
'profile' => profile (array) record for the person from the database 'profile' => profile (array) record for the person from the database
'entry' => the (string) HTML of the generated entry 'entry' => the (string) HTML of the generated entry
**'contact_block_end'** - called when formatting the block of contacts/friends on a profile sidebar has completed ###'contact_block_end'
$b is an array is called when formatting the block of contacts/friends on a profile sidebar has completed.
$b is an array:
'contacts' => array of contacts 'contacts' => array of contacts
'output' => the (string) generated HTML of the contact block 'output' => the (string) generated HTML of the contact block
**'bbcode'** - called during conversion of bbcode to html ###'bbcode'
$b is (string) converted text * called during conversion of bbcode to html
* $b is a string converted text
**'html2bbcode'** - called during conversion of html to bbcode (e.g. remote message posting) ###'html2bbcode'
$b is (string) converted text * called during conversion of html to bbcode (e.g. remote message posting)
* $b is a string converted text
**'page_header'** - called after building the page navigation section ###'page_header'
$b is (string) HTML of nav region * called after building the page navigation section
* $b is a string HTML of nav region
###'personal_xrd'
'personal_xrd' is called prior to output of personal XRD file.
$b is an array:
**'personal_xrd'** - called prior to output of personal XRD file.
$b is an array
'user' => the user record for the person 'user' => the user record for the person
'xml' => the complete XML to be output 'xml' => the complete XML to be output
**'home_content'** - called prior to output home page content, shown to unlogged users ###'home_content'
$b is (string) HTML of section region * called prior to output home page content, shown to unlogged users
* $b is (string) HTML of section region
###'contact_edit'
is called when editing contact details on an individual from the Contacts page.
$b is an array:
**'contact_edit'** - called when editing contact details on an individual from the Contacts page
$b is (array)
'contact' => contact record (array) of target contact 'contact' => contact record (array) of target contact
'output' => the (string) generated HTML of the contact edit page 'output' => the (string) generated HTML of the contact edit page
**'contact_edit_post'** - called when posting the contact edit page ###'contact_edit_post'
$b is the $_POST array * called when posting the contact edit page.
* $b is the $_POST array
**'init_1'** - called just after DB has been opened and before session start ###'init_1'
$b is not used or passed * called just after DB has been opened and before session start
* $b is not used or passed
**'page_end'** - called after HTML content functions have completed ###'page_end'
$b is (string) HTML of content div * called after HTML content functions have completed
* $b is (string) HTML of content div
###'avatar_lookup'
'avatar_lookup' is called when looking up the avatar.
$b is an array:
**'avatar_lookup'** - called when looking up the avatar
$b is (array)
'size' => the size of the avatar that will be looked up 'size' => the size of the avatar that will be looked up
'email' => email to look up the avatar for 'email' => email to look up the avatar for
'url' => the (string) generated URL of the avatar 'url' => the (string) generated URL of the avatar
**'emailer_send_prepare'** - called from Emailer::send() before building the mime message ###'emailer_send_prepare'
$b is (array) , params to Emailer::send() 'emailer_send_prepare' called from Emailer::send() before building the mime message.
$b is an array, params to Emailer::send()
'fromName' => name of the sender 'fromName' => name of the sender
'fromEmail' => email fo the sender 'fromEmail' => email fo the sender
'replyTo' => replyTo address to direct responses 'replyTo' => replyTo address to direct responses
@ -207,16 +259,19 @@ Current hooks:
'textVersion' => text only version of the message 'textVersion' => text only version of the message
'additionalMailHeader' => additions to the smtp mail header 'additionalMailHeader' => additions to the smtp mail header
**'emailer_send'** - called before calling PHP's mail() ###'emailer_send'
$b is (array) , params to mail() is called before calling PHP's mail().
$b is an array, params to mail()
'to' 'to'
'subject' 'subject'
'body' 'body'
'headers' 'headers'
Complete list of hook callbacks
---
A complete list of all hook callbacks with file locations (generated 14-Feb-2012): Please see the source for details of any hooks not documented above. Here is a complete list of all hook callbacks with file locations (as of 14-Feb-2012). Please see the source for details of any hooks not documented above.
boot.php: call_hooks('login_hook',$o); boot.php: call_hooks('login_hook',$o);