There are 14 security groups and no explanation.

Authored by: Tony on Wednesday, January 29 2003 @ 08:54 PM EST

Granted the docs may be lacking in the description of the groups, but I would say if you can read (which, obviously, you can) you can infer their meaning.

For example, StoryAdmin, as it implies, lets a user administer story. Closer inspection shows the story.read, story.edit, story.moderate and story.delete features are tied to this group. Again, those are the actions given to the Group.

The same applies to most of the other groups with the exception of the Root group which, again, should be fairly straightforward to *nix users. Root is the superuser group.

I don't mean to belittle the point, but most of this should be obvious. I will make it a task to get these documented...in the meantime you can post further questions if you have group or right you don't understand.

---
The reason people blame things on previous generations is that there's only one other choice.

[ Reply to This | # ]

Authored by: richschmidt on Wednesday, January 29 2003 @ 11:32 PM EST

While the meanings may be obvious to you, or to others familiar with *nix, the reality is that GL is attracting more and more users like me -- people with very little programming or *nix experience. (I have enough that I can figure most things out, but I certainly don't live in that world.)

There are probably dozens of people out there thinking the same things this poster was brave enough to post: "The GL documentation is useless once you get past the install process. Where is the Admin Documentation?"

Until there's some real documentation, GL will continue to miss a hefty segment of potential users. So... Is anybody working on documentation?

[ Reply to This | # ]

Authored by: Anonymous on Thursday, January 30 2003 @ 01:12 AM EST

<b>I completely agree</b> Geeklog needs better documentation... I can really see it now if you don't... While Geeklog is a free application and you're money is most likely made by donations as I have planned, a good for dummies or learn Geeklog in 24 Hrs might help in raising project funds... Even if that sounds a little deep and you would plan to release a digital manual for free via pdf or what ever, good and better documentation is necessary... It would sorta complete the learning curve circle...

For example I like to read up and search more than I ask questions and their are a few things which make no sense to me at all... BTW, I make a few comments and usually anonymously... How can I keep posted on replies etc? I am losing track... Thanks

[ Reply to This | # ]

Authored by: Blaine on Thursday, January 30 2003 @ 01:18 AM EST

Geeklog is a community that is extending to non-technical users and that is fantastic. It is the voluntary contributions of many that are necessary to benefit all. While much attention has been on developing functionality, there is a need for more user and admin documentation.

Now, this is an area that our non-technical users can contribute most. Any technical questions would would gladly be answered if someone stepped up.

Many of the plugins that are so easily downloaded and installed have takes 100's of hours and it would not take someone anywhere near that time to create some HTML based user and admin documentation.

Any takers?

[ Reply to This | # ]

Authored by: richschmidt on Thursday, January 30 2003 @ 05:57 AM EST

Maybe someone should set up a Wiki for this...

Seems to be a great documentation tool, from what little I've seen so far...

[ Reply to This | # ]

Authored by: Nuke on Thursday, January 30 2003 @ 12:43 PM EST

While I agree that the documentation should be updated and should include this information, I'm afraid I agree that with a minimal effort you could have figured this out for yourself. It's moot at this point though... Hopefully we've given you what you need to continue configuring your system. Care to supply a URL? I'm sure many of us would love to see what you've done.

Nuke...

[ Reply to This | # ]

Authored by: richschmidt on Thursday, January 30 2003 @ 03:59 PM EST

I don't have any GL sites up and running yet. This is very much a side thing for me, trying to get some sites up and running for a church and another couple of non-profit groups in our town. Once I have 'em up and running, I'll be sure to post the URL's.

Heck, if I'm able to spend enough time on this hobby, I'd be glad to join the documentation team, if there is one. :)

- Rich

[ Reply to This | # ]

Authored by: drmagu on Thursday, January 30 2003 @ 05:10 PM EST

Yeah, so I still have not figured out what the difference is between story.moderate, story.submit and story.edit.
I wanted to create a group called "authors", which are registered users who can enter their story while bypassing the submit process. At the same time, they would have access to the "images" function etc., in other words all the story editor stuff. I do not want, however, that these Authors are able to Edit anyone else's work other than their own. So, I created the group with [all users] and [logged-in users] clicked, and I assigned the rights of [story.edit].
Well, partial success! When a user is made a member of Authors, she gets transported to the edit screen when "contributing" a story. Unfortunately, however, she is also able to edit stories from other users, including accepted stories from registered members. What am I missing?
TIA, Dr Magu

[ Reply to This | # ]