How To Install A Geeklog Plugin - Revision history

Dirk: link to plugin installation overview image

2009-06-05T12:29:03Z

link to plugin installation overview image

Dirk: An attempt to update this information

2009-06-04T14:36:14Z

An attempt to update this information

Dirk: added another category

2009-05-08T09:17:32Z

added another category

Dirk: removed note about old auto-install pre-1.3.4

2009-05-06T08:07:42Z

removed note about old auto-install pre-1.3.4

Tomw at 14:43, 2 July 2004

2004-07-02T14:43:32Z

Tomw at 14:33, 2 July 2004

2004-07-02T14:33:32Z

Tomw at 14:33, 2 July 2004

2004-07-02T14:33:00Z

New page

Note: Up until Geeklog version 1.3.4, there was an automatic install procedure for plugins. This, however, caused too many problems and support issues and has been removed from later versions. The manual install as outlined below is now the recommended way to install a plugin and should work for both old and new versions of Geeklog.

For details, you should always refer to the README that comes with the plugin. In general, however, a plugin will be installed like this:

#Depending on your setup and server access, you should either upload the tarball and unpack it remotely or unpack the tarball locally and upload the extracted files and folders afterwards.
#The public_html directory in the tarfile is copied to the webtree under <plugin name>. e.g. if my geeklog web is in /path/to/geeklog/public_html/ then the public_html from the tarfile is copied to /path/to/geeklog/public_html/<plugin name>
#The admin directory in the tarfile is copied to the admin webtree. e.g. if my geeklog admin webtree is in /path/to/geeklog/public_html/admin/ then the admin directory from the tarfile is copied to /path/to/geeklog/public_html/admin/plugins/<plugin name>
#Call the plugins install script at http://yourgeeklogsite/admin/plugins/<plugin name>/install.php
If this is a new install (plugin doesn't exist in plugins table) then table.sql is executed and then data.sql is executed
If this is an upgrade that the necessary upgrade_<version>.sql script is searched for and, if found, executed.
#That's it!

@@ Line 8: / Line 8: @@
 #* If this is an upgrade, then you should find the plugin listed with the other installed plugins, sporting a note asking you to update it. Click on the edit link (the little pen icon). On the next page, you will find an "Update" button. Click it to initiate the plugin update.
 # That's it!
 [[Category:Plugin Development]] [[Category:Plugins]]

@@ Line 2: / Line 2: @@
 # Depending on your setup and server access, you should either upload the tarball and unpack it remotely or unpack the tarball locally and upload the extracted files and folders afterwards.
-# The public_html directory in the tarfile is copied to the webtree under <plugin name>. e.g. if my geeklog web is in /path/to/geeklog/public_html/ then the public_html from the tarfile is copied to /path/to/geeklog/public_html/<plugin name>
+# The <tt>public_html</tt> directory in the tarfile is copied to the webtree under <tt><plugin name></tt>. e.g. if my Geeklog web is in <tt>/path/to/geeklog/public_html/</tt> then the <tt>public_html</tt> from the tarfile is copied to <tt>/path/to/geeklog/public_html/<plugin name></tt>
-# The admin directory in the tarfile is copied to the admin webtree.  e.g. if my geeklog admin webtree is in /path/to/geeklog/public_html/admin/ then the admin directory from the tarfile is copied to /path/to/geeklog/public_html/admin/plugins/<plugin name>
+# The <tt>admin</tt> directory in the tarfile is copied to the admin webtree.  e.g. if my Geeklog admin webtree is in <tt>/path/to/geeklog/public_html/admin/</tt> then the <tt>admin</tt> directory from the tarfile is copied to <tt>/path/to/geeklog/public_html/admin/plugins/<plugin name></tt>
-# Call the plugins install script at http://yourgeeklogsite/admin/plugins/<plugin name>/install.php
+# Log into your Geeklog site and go to the Plugins admin panel (from the [[Admins Block]])
-#* If this is a new install (plugin doesn't exist in plugins table) then table.sql is executed and then data.sql is executed
+#* If this is a new install (plugin doesn't exist in the <tt>gl_plugins</tt> table), then you should find it listed in the "New Plugin" section at the end of the Plugins page. Click on the "Install" link there to initiate the plugin install.
-#* If this is an upgrade that the necessary upgrade_<version>.sql script is searched for and, if found, executed.
+#* If this is an upgrade, then you should find the plugin listed with the other installed plugins, sporting a note asking you to update it. Click on the edit link (the little pen icon). On the next page, you will find an "Update" button. Click it to initiate the plugin update.
 # That's it!
 [[Category:Plugin Development]] [[Category:Plugins]]

← Older revision		Revision as of 09:17, 8 May 2009
Line 10:		Line 10:


−	[[Category:Plugin Development]]	+	[[Category:Plugin Development]] [[Category:Plugins]]

← Older revision		Revision as of 14:43, 2 July 2004
Line 10:		Line 10:
	#*If this is an upgrade that the necessary upgrade_<version>.sql script is searched for and, if found, executed.		#*If this is an upgrade that the necessary upgrade_<version>.sql script is searched for and, if found, executed.
	#That's it!		#That's it!
		+
		+	[[Category:Plugin Development]]

@@ Line 1: / Line 1: @@
-Note: Up until Geeklog version 1.3.4, there was an automatic install procedure for plugins. This, however, caused too many problems and support issues and has been removed from later versions. The manual install as outlined below is now the recommended way to install a plugin and should work for both old and new versions of Geeklog.
+For details, you should always refer to the README that comes with the plugin. In general, however, a plugin will be installed like this:
-For details, you should always refer to the README that comes with the plugin. In general, however, a plugin will be installed like this:
+# Depending on your setup and server access, you should either upload the tarball and unpack it remotely or unpack the tarball locally and upload the extracted files and folders afterwards.
 [[Category:Plugin Development]]

@@ Line 7: / Line 7: @@
 #The admin directory in the tarfile is copied to the admin webtree.  e.g. if my geeklog admin webtree is in /path/to/geeklog/public_html/admin/ then the admin directory from the tarfile is copied to /path/to/geeklog/public_html/admin/plugins/<plugin name>
 #Call the plugins install script at http://yourgeeklogsite/admin/plugins/<plugin name>/install.php
-If this is a new install (plugin doesn't exist in plugins table) then table.sql is executed and then data.sql is executed
+#*If this is a new install (plugin doesn't exist in plugins table) then table.sql is executed and then data.sql is executed
-If this is an upgrade that the necessary upgrade_<version>.sql script is searched for and, if found, executed.
+#*If this is an upgrade that the necessary upgrade_<version>.sql script is searched for and, if found, executed.
 #That's it!