Difference between revisions of "How To Install A Geeklog Plugin"
From GeeklogWiki
(removed note about old auto-install pre-1.3.4) |
m (added another category) |
||
Line 10: | Line 10: | ||
− | [[Category:Plugin Development]] | + | [[Category:Plugin Development]] [[Category:Plugins]] |
Revision as of 09:17, 8 May 2009
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!