| Re: Improving the management of groups |
| by rt1c on 2012/3/25 14:25:49 Just downloaded Xoops will look into how to Improve the management of groups. |
| Re: Improving the management of groups |
| by redheadedrod on 2012/3/25 14:25:42 Quote:
If I understand what he is saying, basically each branch may have different structures and so he ends up needing a separate group for each one. Essentially the only group that multiple members can belong to are the lowest level employees. If the structure at each branch and through out the whole system was the same then what you say is correct. However if you have a dozen or more modules installed this could take a week or more to work the bugs out of just the permissions. However with an ACL or similar the same job could likely be done in an afternoon. I do see the reason behind what he is asking. Even with 15 groups it can take a couple days to get the permissions worked out with the current system. I think we might be able to do better. Also here is an example of one being done now as well... http://groups.drupal.org/node/205928 At this time I will still say I think it can be done in a manner that we can change the system without it affecting modules. I will see if I can make it work. But this is much more involved than the other group changes so it may take a bit to accomplish. |
| Re: Improving the management of groups |
| by redheadedrod on 2012/3/25 14:14:09 I will look into this further as I said, I think that the permission system can be revamped without affecting the modules because the system will simply just tell the module if a user has a permission or not. It should be a simple matter to be able to modify those permissions behind the scenes before the module sees them. My first thought was to add a User based over ride per module. I may still do that depending on if it looks to be not needed. This php gacl looks promising but I would have to rewrite it to work with Xoops. The idea seems solid and it appears to be relatively simple so It shouldn't require much to pull the core of it out. This system is designed to work out of the box as an add on to most systems and it adds things most of us do not need or would be done differently. At the moment I will be looking into the groups system altogether and as it looks now I will look at the following. Group based theme support Group Permission system Revamp (as already discussed above) Group members utility (Think the group membership system to replace the current system) Group based membership system. This will support things such as password expiration, group membership depending on profile questions (Think Male/Female as example) , subscription support. To support subscriptions there will be a time system added that will allow someone's group to be changed automatically. This could be used to expire passwords, have a waiting period for users before they become full members or simply subscriptions. Would also support bans that could expire automatically etc. Up to the imagination of the webmaster. This will simply have an expiration setup to change the group. To support subscriptions an add on module will need to be used. I expect that any current subscription module should work with this system as is but you will have a more powerful system to work with. Again, these will be done as a drop in replacement and will be designed to work with the latest stable version. If they work well I would hope they get included into 2.6 at some point. |
| Re: Improving the management of groups |
| by zyspec on 2012/3/25 14:00:06 Do all of the roles (independent of location) have the same rights? If so then you can create groups that give 'directors' a certain set of rights and a 'location' group having another set of rights. Then you just add people to multiple groups (say 'trader' and 'Memphis' groups) to give them all of the permissions they need. This only requires 15 groups (5 for locations, 10 for roles). Just a thought.... |
| Re: Improving the management of groups |
| by redheadedrod on 2012/3/24 0:40:23 The concept of PHPGACl is a solid one and could possibly be added to Xoops. I will look into this further after I get further with the Stuff I am currently working on. The organic permissions as mentioned for Drupal are user based and not system based. Those are more to make a permissions system like the one for Facebook or something similar. Note that I should mention when I say look into the MOST I am able to do at this time is to write "hacks" for xoops and hope that the concept works and is something that gets added to 2.6. I am not a core programmer. If I build something it will be a sort of "drop in" solution that will be specific to a specific version of Xoops. This will be the case for any of my Group update stuff. |
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $15.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
|
|