Search results

Jump to: navigation, search

Page title matches

  • ...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
  • Plugin Development Doc from Geeklog Distribution. *[[Preparing your Geeklog Plugin Distribut]]ion
    661 B (70 words) - 01:08, 3 December 2004

Page text matches

  • == Geeklog Plugin Developers Handbook == # [[How to get Started: A Development Overview]]
    4 KB (626 words) - 19:53, 21 April 2010
  • ...ll global variables with an underscore, so global variables in the Contact plugin start with <code>$_CT_</code>. [[Category:Plugin Developers Handbook]] [[Category:Plugin Development]]
    4 KB (534 words) - 17:53, 21 May 2009
  • ...ation of themes. Your use of templates will make it easier to include your plugin or block in the theme system. ...lated without changing the code. The use of language files will allow your plugin or block to also be used worldwide without the changing of your code. Geekl
    1 KB (222 words) - 14:31, 8 June 2009
  • Time will be well spent by the Geeklog plugin or block developer to become familiar with several Geeklog libraries. The f The Geeklog plugin or block developer should have a good understanding of <tt>lib-common.php</
    12 KB (1,854 words) - 18:37, 16 April 2010
  • ...lock]] is code added to <tt>lib-custom.php</tt> and is then defined by the plugin editor. But what are the other differences and why as a developer would I c ...P code to execute a query to return a list of the last 10 comments, links, plugin records and return the formatted results
    7 KB (1,139 words) - 19:36, 23 May 2009
  • ... you should make before you begin development of either your block or your plugin. ...his documentation you will find references to {plugin-name}. The value of {plugin-name} is the name you choose here.
    5 KB (933 words) - 19:37, 23 May 2009
  • ...at are located outside the webtree, like those located in the <tt>plugins/{plugin}</tt> directory, then put them in a directory called <tt>blocks/{block}</tt ...ow we will assume that you are creating a plugin named 'greatplugin'. Each plugin must have three separate directories.
    3 KB (395 words) - 17:42, 16 May 2009
  • ...compatible with earlier Geeklog versions. The [[Plugin Autoinstall]] and [[Plugin Auto-Uninstall]], as available in newer Geeklog releases, makes these steps ...n overview of this code function and the overall relationship to the other plugin code.
    9 KB (1,565 words) - 18:00, 21 May 2009
  • Version: Nov 10, 2002 (Release Date for Chatterblock 3.0 as a plugin)<br> This is a true Geeklog plugin using the Geeklog Plugin API calls.
    14 KB (2,093 words) - 21:32, 23 May 2009
  • // | File Management Plugin v1.0 for Geeklog - The Ultimate Weblog | // | Plugin. By default this program will automatically create all required |
    22 KB (2,424 words) - 13:27, 19 April 2010
  • ... the stats page is a more detailed report for each Geeklog component. Your plugin can be written to return results for both or just one of these sections. ...er of files in your file repository or some other overall counter for your plugin. This will be a straight forward database query to return the count and des
    7 KB (1,091 words) - 16:20, 24 May 2009
  • This section describes and documents how to enable your plugin to use the Geeklog comment engine. This is a key feature or plugin functionality for many developers and not very difficult to integrate into
    17 KB (2,623 words) - 19:45, 2 January 2013
  • ...ed on this page are meant for Geeklog v1.5 and below. They make use of the Plugin() class which will eventually be phased out. Tying your plugin into Geeklogs search API is rather easy. Easy, that is, if you know how se
    6 KB (984 words) - 21:40, 20 October 2009
  • This section will describe and document how to enable your plugin to use the Geeklog moderation engine. ...ncludes submitting of an item that needs to be reviewed by a site admin or plugin admin before posting to the site. The Geeklog (GL) developers have made th
    14 KB (1,989 words) - 17:28, 31 March 2010
  • Distribution of your plugin should be in a tarball with specific naming requirements. {plugin}_{plugin version}_{geeklog version}.tar.gz
    1 KB (212 words) - 18:09, 24 May 2009
  • The following section outlines the Geeklog [[Plugin API]] functions which you ...useroption_mycontacts() does not exist, it is skipped and the next enabled plugin is checked.
    8 KB (1,136 words) - 18:45, 16 April 2010
  • ...e:''' The Universal Plugin Toolkit may eventually be replaced with a new [[Plugin Toolkit]]. ...the [[Plugin API]] in Geeklog and get down to the business of writing your plugin application. It consists of all the necessary files you will need to interf
    3 KB (518 words) - 21:49, 10 January 2016
  • ... making some entries in the Geeklog database to let Geeklog know that your plugin is there. ... Size doesn't matter. There is no limit after which you have to make it a plugin.
    28 KB (4,488 words) - 17:36, 11 August 2011
  • The [[FAQ Manager Plugin]] helps you organize and maintain Frequently Asked Questions. The [[File Management Plugin]] lets you create a download area on your website.
    2 KB (218 words) - 17:13, 21 May 2009
  • For a plugin to use the built-in RSS content syndication it needs to implement three fun where pluginname is the name of the plugin.
    3 KB (330 words) - 18:15, 24 May 2009

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

Personal tools
Namespaces

Variants
Views
Actions
documentation
Tools