"Seems like a bad idea to rename folders since one may forget then what it originally was and where to move it. Maybe not a problem in UNIX (don't know the commands), but sure can be in Mac OS X. Seems like there should be a folder that is named: move.the.contents.to.public_html directory and similarly move.contents.to.public_html/admin/plugins directory or some such. Of course the directory structure would have been set up differently if someone was doing this all over again. Probably wasting my keystrokes as too hard to change now.
I may get sort of used to it, but every program has its own conventions and one doesn't do it every day. I'm running phpBB and haven't touched it in maybe six months. Doubt I'd remember how it's put together. But free is free. Thanks to everyone for putting all this together.
On Thursday, Jun 19, 2003, at 10:00 US/Pacific, [EMAIL PROTECTED] wrote:
Geeklog plugin convention generally is as follows:
1) you unpack a plugin into <geeklog_root>/plugins/ directory
In the newly created plugin directory you'll see a sub directory "admin" and sub-directory "public_html".
It is not very intuitive, but you have to move AND rename these two directories.
2) "public_html" is *renamed* to the name of plugin (in your case it will be called "lists") and moved *under* public_html directory of your
geeklog installation. So your webserver accessible directory will look like this: /public_html/lists/
3) "admin" dorectory is renamed to the name of plugin (in your case "lists") and moved under /public_html/admin/plugins/
so you'll have your webserver doc directory:
/public_html/admin/plugins/lists
You obviously do not do anything with geeklog public_html directory and to geeklog index.php
That's all. When you install a couple of plugins you'll get used to it :)
