Plugins - Revision history

Dirk: removed a sentence

2009-06-08T10:08:22Z

removed a sentence

Dirk: added a headline and a link to Disabling a plugin

2009-06-05T12:27:10Z

added a headline and a link to Disabling a plugin

Dirk: re-labeled links

2009-05-21T16:59:29Z

re-labeled links

Dirk: a few links and minor updates/corrections

2009-05-20T10:48:51Z

a few links and minor updates/corrections

LWC: Fixed links

2009-05-19T00:29:05Z

Fixed links

Cordiste at 21:41, 18 May 2009

2009-05-18T21:41:40Z

Dirk: Added category

2009-04-29T14:12:17Z

Added category

Dirk: Re-save, in the hope that it makes the images appear ...

2008-06-12T18:45:00Z

Re-save, in the hope that it makes the images appear ...

Blaine at 17:22, 1 August 2004

2004-08-01T17:22:04Z

Blaine at 17:20, 1 August 2004

2004-08-01T17:20:25Z

@@ Line 1: / Line 1: @@
-Geeklog plugins are addon components that provide new functionality and leverage the internal services of Geeklog. Many of the available and contributed plugins are listed in this document. Plugins are different then [[Blocks]] which normally do not use any of the internal Geeklog services (API's).
+Geeklog plugins are addon components that provide new functionality and leverage the internal services of Geeklog. Plugins are different then [[Blocks]] which normally do not use any of the internal Geeklog services ([[Plugin API|APIs]]).
 For a list of available plugins (note: work in progress), see
@@ Line 9: / Line 9: @@
 Plugins will for example automatically add themselves to your site navigation and provide the ability to restrict and control access to the component for public access and administrative functions.
-Geeklog Plugins have access to the following services or API's
+Geeklog Plugins have access to the following services or APIs
 * Plugin Editor to install/de-install and enable/disable plugins
-* Provide links to the SiteHeader Navigation, [[User Settings & User Functions Block|User]] and [[Admins Block|Admin]] Menus
+* Provide links to the Site Header Navigation, [[User Settings & User Functions Block|User]] and [[Admins Block|Admin]] Menus
 * Add to the site search function
 * Extend the site stats reporting

@@ Line 30: / Line 30: @@
 In addition, each plugin may have other steps that need to be performed so read the plugin installation directions carefully.
 As an overview to assist you with installing a plugin, here is an illustrated image that describes the directory structure and locations of the plugin related folders and files. [[Image:PluginInstallOverview.jpg]]
@@ Line 43: / Line 45: @@
 Note: If there are any errors during installation, the plugin will (should) by default remove itself and delete the added tables.
-Troubleshooting: Review the Geeklog <tt>error.log</tt> file for a detailed trace of the installation for any related errors if the install is not successful.
+Troubleshooting:
 The following illustrated image shows the Plugin Editor with an overview of its usage.

@@ Line 1: / Line 1: @@
 Geeklog plugins are addon components that provide new functionality and leverage the internal services of Geeklog. Many of the available and contributed plugins are listed in this document. Plugins are different then [[Blocks]] which normally do not use any of the internal Geeklog services (API's).
-* See [[Official Plugins]]
+For a list of available plugins (note: work in progress), see
-* See [[Unofficial Plugins]]
+* [[Official Plugins|Bundled Plugins]]
 There are many services that a plugin can use to provide a tightly coupled application that now performs and looks like it a natural part of the overall Geeklog solution. It's possible to just wrap Geeklog around another application but it may have it's own security and user model for example. It's far better to have a single user database and security model to manage users and access to site features.

@@ Line 1: / Line 1: @@
-Geeklog plugins are addon components that provide new functionality and leverage the internal services of Geeklog. Many of the available and contributed plugins are listed in this document. Plugins are different then blocks which normally do not use any of the internal Geeklog services (API's).
+Geeklog plugins are addon components that provide new functionality and leverage the internal services of Geeklog. Many of the available and contributed plugins are listed in this document. Plugins are different then [[Blocks]] which normally do not use any of the internal Geeklog services (API's).
 * See [[Official Plugins]]
 * See [[Unofficial Plugins]]
-There are many services that a plugin can use to provide a tightly coupled application that now performs and looks like it a natural part of the over all Geeklog solution. It's possible to just wrap Geeklog around another application but it may have it's own security and user model for example. It's far better to have a single user database and security model to manage users and access to site features.
+There are many services that a plugin can use to provide a tightly coupled application that now performs and looks like it a natural part of the overall Geeklog solution. It's possible to just wrap Geeklog around another application but it may have it's own security and user model for example. It's far better to have a single user database and security model to manage users and access to site features.
 Plugins will for example automatically add themselves to your site navigation and provide the ability to restrict and control access to the component for public access and administrative functions.
@@ Line 10: / Line 10: @@
 Geeklog Plugins have access to the following services or API's
 * Plugin Editor to install/de-install and enable/disable plugins
-* Provide links to the SiteHeader Navigation, User and Admin Menu's
+* Provide links to the SiteHeader Navigation, [[User Settings & User Functions Block|User]] and [[Admins Block|Admin]] Menus
 * Add to the site search function
 * Extend the site stats reporting
-* Leverage the GL Comment Engine
+* Leverage the Geeklog Comment Engine
 * Automatically update tables upon user add/edit/delete
 * Extend the User Account Profile - add new options
@@ Line 19: / Line 19: @@
 * Provide new RSS Newsfeeds
 * Provide a formatted Centerblock
-* Integrate into the WhatsNew block
+* Integrate into the [[What's New Block]]
 Plugins can be complete applications or provide a new administrative service but they all need to support a minimum set of features to be called a plugin.
-* Support the Plugin Editor Install/De-install
+* Support the Plugin Editor Install/Uninstall
 * Provide new security rights such as plugin_name.edit and plugin_name.user
 * Provide menu integration
 Plugins all have a similar installation procedure which requires a few manual steps to copy the plugin related files to the required directories. This part of the plugin installation is often confusing for new users/site admins. This is understandable but once you do one plugin, you will find others much easier to install.
 In addition, each plugin may have other steps that need to be performed so read the plugin installation directions carefully.
-As an overview to assist you with installing a plugin, I have created an illustrated image that describes the directory structure and locations of the plugin related folders and files. [[Image:PluginInstallOverview.jpg]]
+As an overview to assist you with installing a plugin, here is an illustrated image that describes the directory structure and locations of the plugin related folders and files. [[Image:PluginInstallOverview.jpg]]
 Once the files are copied and in place as required, you will use the Admin Plugin Editor to complete the installation. The plugin editor will automatically list new un-installed plugins if the files have been copied correctly. If not - then review your previous steps.
-The plugin editor will call the plugin install or de-install functions - which are part of the new plugin program files. The installation process will
+The plugin editor will call the plugin install or uninstall functions - which are part of the new plugin program files. The installation process will
 * Create all required new tables
 * Add any new default data
@@ Line 44: / Line 42: @@
 Note: If there are any errors during installation, the plugin will (should) by default remove itself and delete the added tables.
-Troubleshooting: Review the Geeklog error.log file for a detailed trace of the installation for any related errors if the install is not successful.
+Troubleshooting: Review the Geeklog <tt>error.log</tt> file for a detailed trace of the installation for any related errors if the install is not successful.
-The following illustrated image shows the Plugin Editor with an overview of it's usage.
+The following illustrated image shows the Plugin Editor with an overview of its usage.
 [[Image:PluginEditor.jpg]]
 [[Category:Plugins]]

@@ Line 1: / Line 1: @@
 Geeklog plugins are addon components that provide new functionality and leverage the internal services of Geeklog. Many of the available and contributed plugins are listed in this document. Plugins are different then blocks which normally do not use any of the internal Geeklog services (API's).
-* See [[Official_Plugins|Official Plugins]]
+* See [[Official Plugins]]
-* See [[UnOfficial_Plugins|Unofficial Plugins]]
+* See [[Unofficial Plugins]]
 There are many services that a plugin can use to provide a tightly coupled application that now performs and looks like it a natural part of the over all Geeklog solution. It's possible to just wrap Geeklog around another application but it may have it's own security and user model for example. It's far better to have a single user database and security model to manage users and access to site features.

← Older revision		Revision as of 21:41, 18 May 2009
Line 1:		Line 1:
	Geeklog plugins are addon components that provide new functionality and leverage the internal services of Geeklog. Many of the available and contributed plugins are listed in this document. Plugins are different then blocks which normally do not use any of the internal Geeklog services (API's).		Geeklog plugins are addon components that provide new functionality and leverage the internal services of Geeklog. Many of the available and contributed plugins are listed in this document. Plugins are different then blocks which normally do not use any of the internal Geeklog services (API's).
		+
		+	* See [[Official_Plugins\|Official Plugins]]
		+	* See [[UnOfficial_Plugins\|Unofficial Plugins]]
		+

	There are many services that a plugin can use to provide a tightly coupled application that now performs and looks like it a natural part of the over all Geeklog solution. It's possible to just wrap Geeklog around another application but it may have it's own security and user model for example. It's far better to have a single user database and security model to manage users and access to site features.		There are many services that a plugin can use to provide a tightly coupled application that now performs and looks like it a natural part of the over all Geeklog solution. It's possible to just wrap Geeklog around another application but it may have it's own security and user model for example. It's far better to have a single user database and security model to manage users and access to site features.

← Older revision		Revision as of 14:12, 29 April 2009
Line 45:		Line 45:
	The following illustrated image shows the Plugin Editor with an overview of it's usage.		The following illustrated image shows the Plugin Editor with an overview of it's usage.
	[[Image:PluginEditor.jpg]]		[[Image:PluginEditor.jpg]]
		+
		+
		+	[[Category:Plugins]]

← Older revision		Revision as of 18:45, 12 June 2008
Line 44:		Line 44:

	The following illustrated image shows the Plugin Editor with an overview of it's usage.		The following illustrated image shows the Plugin Editor with an overview of it's usage.
−	[[Image:~~pluginEditor~~.jpg]]	+	[[Image:PluginEditor.jpg]]