-
...lugins so that Geeklog fits their needs. With that said, Geeklog now has a Plugin Application Program Interface (API).
...debase that allows functions of plugins to be called. This will allow your plugin the following features:
2 KB (372 words) - 11:54, 8 June 2009
-
...mitations in the current Geeklog codebase that will force you to name your plugin tables used for submission in a specific manner. All moderated Geeklog item
...ick <tt>bookreviews</tt> for your main table (this '''must''' also be your plugin name you pick) and then your submission table '''must''' be named <tt>bookr
3 KB (451 words) - 18:20, 18 May 2009
-
If you want your plugin to effect the Admin and User Function blocks
<td valign="top" class="codeheader">plugin_adminoptions_<plugin name></td>
2 KB (256 words) - 07:43, 6 May 2009
-
This plugin API function suffers from a variety of bugs and bad design decisions for wh
...ode>, was originall documented as being 1 for the site stats and 0 for the plugin-specific stats. However, the latter was always called with a value of '''2'
3 KB (454 words) - 18:41, 18 May 2009
-
If you want to give your plugin the ability to uninstall itself then you must implement this function.
<td valign="top" class="codeheader">plugin_uninstall_<plugin
2 KB (328 words) - 08:05, 6 May 2009
-
<td valign="top" class="codeheader">plugin_user_create_<plugin name></td>
<td valign="top" class="codeheader">plugin_user_delete_<plugin name></td>
1,005 bytes (146 words) - 14:08, 7 July 2007
-
...<td valign="top" class="codeheader">plugin_profilevariablesedit_<plugin name></td>
...d when Geeklog is about to display the edit form for a user's profile. The plugin is given the user id and a reference to the template of the edit form. It c
3 KB (420 words) - 14:42, 2 July 2004
-
<td valign="top" class="codeheader">plugin_centerblock_<plugin name></td>
...es during rendering of the site's index page. The parameters will tell the plugin where on the index page the block would appear.<br>
3 KB (426 words) - 18:55, 25 December 2008
-
...[[
Plugin API]] is just that - an API. You obviously have to write all your
plugin code yourself. We have put stubs in place to link to your Admin Interface.
<pre>http://yourgeeklogdomain/admin/plugins/<
plugin name>/ </pre>
680 bytes (116 words) - 14:26, 4 June 2009
-
== The plugin tarfile ==
All Geeklog plugin tarfiles should use the following naming convention:
3 KB (446 words) - 12:55, 4 June 2009
-
...ays refer to the README that comes with the plugin. In general, however, a plugin will be installed like this:
..._html</tt> from the tarfile is copied to <tt>/path/to/geeklog/public_html/<plugin name></tt>
2 KB (293 words) - 12:29, 5 June 2009
-
...our site where it can be downloaded by Geeklog users. You can sumbit your plugin to our site at http://www.geeklog.net.
[[Category:Plugin Development]]
520 bytes (85 words) - 14:43, 2 July 2004
-
Plugin Development Doc from Geeklog Distribution.
*[[Preparing your Geeklog Plugin Distribut]]ion
661 bytes (70 words) - 01:08, 3 December 2004
-
...for all older plugins. The Geeklog Development Team strongly suggest when plugin developers are upgrading their plugins that they take the time to convert a
== Theme Specific Plugin Templates ==
12 KB (2,019 words) - 14:56, 27 December 2015
-
This API function informs a plugin about the change of state of another plugin:
...lugin whose state has just changed. <code>$status</code> informs about the plugin's new state and can be one of the following:
866 bytes (128 words) - 20:14, 1 May 2009
-
...ciated functions COM_siteHeader and COM_siteFooter. If you are unsure if a plugin supports Geeklog v2.2.0 then either disable it before you upgrade Geeklog,
*# [[Getting Started]] with Geeklog Development
2 KB (278 words) - 17:22, 27 September 2022
-
## [[Plugin Development]]
### [[Plugin Developers Handbook]]
2 KB (213 words) - 21:47, 10 January 2016
-
*If you had any plugins installed (besides the Static Pages plugin), you should now upload their files on the new server as well (don't run an
...of this writing, PHP 5 is still in Beta. As one of the main goals of PHP 5 development was to keep compatibility with PHP 4, we do not expect any serious problems
11 KB (1,930 words) - 20:39, 25 March 2010
-
...covered. These issues include scalability, performance and weakness is the plugin API.
...improve all of these areas. This document draws out the plans for the GL2 plugin API. Until the first official release of GL2, this document can be consider
15 KB (2,138 words) - 03:37, 23 January 2005
-
##[[Plugin APIG2|Plugin API]]
##[[Core DevelopmentG2|Core Development]]
1 KB (105 words) - 18:02, 11 June 2007
