aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorfriendica <info@friendica.com>2013-10-16 21:50:09 -0700
committerfriendica <info@friendica.com>2013-10-16 21:50:09 -0700
commit2cf136b1861b10e02158fcd34fb6814d0ed9e324 (patch)
treef14e670c926fb3167b9a48a48528981b20ee1630
parentda738134875ac9a5640b2361d18146283da784e4 (diff)
downloadvolse-hubzilla-2cf136b1861b10e02158fcd34fb6814d0ed9e324.tar.gz
volse-hubzilla-2cf136b1861b10e02158fcd34fb6814d0ed9e324.tar.bz2
volse-hubzilla-2cf136b1861b10e02158fcd34fb6814d0ed9e324.zip
wrong function name
-rw-r--r--doc/Plugins.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/Plugins.md b/doc/Plugins.md
index aec4c8399..6b4058443 100644
--- a/doc/Plugins.md
+++ b/doc/Plugins.md
@@ -47,7 +47,7 @@ In our case, we'll call them randplace_load() and randplace_unload(), as that is
* pluginname_uninstall()
-Next we'll talk about **hooks**. Hooks are places in the Red Matrix code where we allow plugins to do stuff. There are a lot of these, and they each have a name. What we normally do is use the pluginname_register() function to register a "handler function" for any hooks you are interested in. Then when any of these hooks are triggered, your code will be called.
+Next we'll talk about **hooks**. Hooks are places in the Red Matrix code where we allow plugins to do stuff. There are a lot of these, and they each have a name. What we normally do is use the pluginname_install() function to register a "handler function" for any hooks you are interested in. Then when any of these hooks are triggered, your code will be called.
We register hook handlers with the 'register_hook()' function. It takes 3 arguments. The first is the hook we wish to catch, the second is the filename of the file to find our handler function (relative to the base of your Red Matrix installation), and the third is the function name of your handler function. So let's create our randplace_load() function right now.