Does anyone know of a way in XOOPS to implement basic hierarchical user management?

What I have is a private XOOPS site where registration is handled solely by the administrator. The users and groups of that site, although small in number at any given time, may be quite dynamic from time to time so need to be added and managed as required by someone other than the admin user.

I've discovered in XOOPS 2.2.2 that the ability to add, edit, delete and otherwise manage users and groups appears to be an all or nothing situation. If I go into admin>users>groups>modify for the selected group and check "Groups" in the "System Admin Rights" section, anyone in that group has the ability to delete any XOOPS user, including themselves and the admin users.

What I need is the ability to have one group, probably with only one member, who can add, edit and delete users and groups as needed for their purposes but NOT have the ability to change anything that is system critical. In other words, permission to do whatever they want to something at or below their permission level but cannot touch anything higher than their permission level.

I've searched through the XOOPS site but haven't been able to find anything relevant to this particular need. And of course there's that little voice in my head that keeps saying "It's such an obvious need, surely I must be missing something." But if I am, I must be blind.

So... any ideas or suggestions on how this situation might best be handled?

Thanks for your time.

jaquita

Speaking of modules and wishes, since we *are* on that topic :) is it possible for the core to provide some kind of functionality for small plugins? The ability to print to pdf or file, do special text formatting and other small dedicated tasks could be handled by something like "minimods".

They wouldn't be part of the core OR a full blown module. Just some utility functions that can register themselves somewhere and then module authors can call them if available.

And of course, I need this functionality last year and can I get a cup of coffee with that too, please?

jaquita

Hi ummpur,

Those are error messages coming from php. I saw a lot of those when I tried to use php 4.4.0 under Linux. If I used php 4.3.xx or php5+ they didn't happen.

jaquita

Quote:

rotflmao If we can have a XOOPerman can we also have a XOOPERuser for us Linux users?

jaquita

Quote:

And take so much abuse in the process to boot!

Actually, I went back and read most of the old threads and gripes and complaints from over the past year or so and I'll have to admit it was the way the XOOPS community ultimately responded to adversity that finally made up my mind to use XOOPS instead of something else.

Some of these folks have walked through fire and have come out it stronger, better and more determined than before. The XOOPS development community now has clearly defined goals, very capable leadership, an enthusiastic support team and seem to be getting very active again after taking a much needed break.

Six months ago I looked at Xoops, liked what I saw but walked away from it because it was in a state of turmoil. Who wants to use a piece of software whose future appears threatened? From the standpoint of a casual observer the message was not reassuring.

I looked at XOOPS again two weeks ago, reviewed the events that have taken place since the first of the year, assessed it's current state and made my decision. The project might be wounded and scarred from battle, but you know what? These guys are not only still standing, they're still moving forward.

I find that very reassuring.

jaquita

Thanks for your reply, broadcircle.

Quote:

I know I can do 4 (above) from admin area. I was hoping admin area would do 1,2 and 3 as well.

I guess what I'm looking for is something like the "attach file" functionality when posting a forum message. Something that presents a button that says "Browse..." that allows you to browse your local filesystem for the file you want then when you click the "Upload" button it gets your local file, uploads it to the remote site and unpacks it into the module directory. At that point the installation and activation would continue as normal.

It's just one of those things that is not necessarily required but it makes installing new modules just a little bit easier.

jaquita

Or if they were a kid rock band they could be called "The XoobieDoos"

jaquita

I rediscovered the developer forums and the XOOPS CVS last night and I can tell you Mith and the devs (ha, sounds like the name for a 60's band) have been very busy in both places.

I also discovered from reading those forums that, believe it or not, developers have lives! I mean, I didn't know that. Did you know that? And here I thought they were all chained like slaves to their computers.

All kidding aside, I'm fairly new here as well and was beginning to have some of my own concerns. From reading the dev forums it looks like almost everyone took a badly needed summer vacation and activity is now starting to build again.

Looks like exciting times ahead!

jaquita

Are there any modules or add-ons or something I'm missing that would allow the admin to upload, unpack and install a new module completely within the admin area?

I'm guessing I can use the upload feature of a few of the modules to get something uploaded. Or I can always scp the file there then ssh in and unpack it and place it in the modules directory.

I'm just wondering if XOOPS admin area has something that can handle this process, not necessarily all at once but at least all in one place.

It would be a convenient feature to have.

jaquita

If you are using xoops-2.2.3 (maybe earlier version db's are the same, I'm not sure) and phpMyAdmin 2.6.1:


1. select the XOOPS database you configured when you installed xoops

2. in the list of tables, find the one that's called "config" preceded by the prefix you defined when you installed xoops. For instance, my table prefix is "x" so my config table is called "x_config".

3. click on the config table to open it

4. look at the tabs across the top of the phpmyadmin page and one of them will say "Browse".

5. click on the "Browse" tab and all the records in the config table will be listed.

6. look in the column labeled "conf_title" for an entry called "_MD_AM_SESSEXPIRE"

7. click on the little pencil looking button on the same line as "_MD_AM_SESSEXPIRE" to edit the record

8. in the field called "conf_value" enter a new value, in minutes, for the new expire time

9. click on the "Go" button at the bottom of the page to save your changes

10. pray....

Since you don't state what version of XOOPS you are using or what version of phpmyadmin hopefully this will get you far enough along to do what you need.

Good luck.

jaquita