Geeklog Forums

Installed latest menu plugin. My topics are organized as normal for the plugin.

Lets say I have two topics:

"topic_" and "topic_01".

If I post to "topic_01" the article shows up in both "topic_01" AND in "topic_".

I need help. Anyone knows what's wrong?

I am about plum tuckered out, having suffered through this for so many hours. But I think I finally figured out the problem. When the thing worked, I nearly cried.

Just in case someone runs into this problem. It seems the solution to it has to do with a sql statement around line 138 in the 1.3.8 version of the index.php files included with the menu plugin.

The following statment is apparently incorrect.
$sql .= " AND left(tid, length('topic')) = '$topic' ";

the line should simply read $sql .= " AND tid = '$topic' ";
(include the double quotes).
-------

I still need someone to at least give me a little "heads up" on allowing users LIMITED group admin rights. Is there a way to let a user administer some groups, but block them from accessing others? I want one of my users to assign certain basic groups to other users, but not get access to the root, plugins and block groups.

If I can get through this, I'd be very pleased.

If a user A in the Group Admin group can assign users to groups that A is not a member of, that sounds like a bug to me. If it hasn't been reported already, you should do so.

If you get a chance, try this:

1. As Admin, create a user. Give her only "all users", "logged-in user" and "group admin" rights.

You don't really need the user to be able to create groups. But unfortunately GL requires "group admin" rights if you are to assign users to groups. You want this user to be able to make either duplicates of herself or less.

2. Now, log in as the user. Go into User Admin. Click on your own name (or even any other user). You should be able to make yourself or anyone else a ROOT user, thereby controlling the entire site.

My problem with this is that after a lot of very hard work a late nights (and early mornings), the user who will maintain the site for us is going to accidentally destroy it. Moreover, her password may get into wrong hands. It is just best to avoid having her have access to or the ability to get access to groups higher than what she has.

Is there a way that perhaps I can create a group, call it "subAdmin" so that if when a users is editing another user that user is in the subadmin group, root, block admin, plugin admin, menu admin, staticpage admin, etc., are unavailable?

The problem with a group admin being able to become root is already known and a fix is in the works.

bye, Dirk