diff options
| author | redmatrix <redmatrix@redmatrix.me> | 2015-11-05 20:49:25 -0800 |
|---|---|---|
| committer | redmatrix <redmatrix@redmatrix.me> | 2015-11-05 20:49:25 -0800 |
| commit | 12db46dcad7cddcc97d4343cd81cfd42498c93b6 (patch) | |
| tree | b3a204d197e7711f76fa20ea87a238454bfaedba | |
| parent | 9e6547a887856efea850f9dd470e2dfbac3345e7 (diff) | |
| download | volse-hubzilla-12db46dcad7cddcc97d4343cd81cfd42498c93b6.tar.gz volse-hubzilla-12db46dcad7cddcc97d4343cd81cfd42498c93b6.tar.bz2 volse-hubzilla-12db46dcad7cddcc97d4343cd81cfd42498c93b6.zip | |
a bit of explanation at the beginning
| -rw-r--r-- | doc/hooklist.bb | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/hooklist.bb b/doc/hooklist.bb index 06b3e6de7..9e0220013 100644 --- a/doc/hooklist.bb +++ b/doc/hooklist.bb @@ -1,3 +1,8 @@ +[h2]Hooks[/h2] + +Hooks allow plugins/addons to "hook into" the code at many points and alter the behaviour or otherwise perform independent actions when an activity takes place or when certain data structures are accessed. There are many hooks which allow you to tie into the software at most any point and do something slightly different than the default thing. These hooks are passed two variables. The first is the App structure which contains details about the entire state of the page request as we build the resulting page. The second is unique to the specific hook that is called and provides specific detail about what is happening in the software at the time the hook is invoked. + + [zrl=[baseurl]/help/hook/module_mod_aftercontent]module_mod_aftercontent[/zrl] General purpose hook for any module, executed after mod_content(). Replace 'module' with module name, e.g. 'photos_mod_aftercontent'. |