Hallo!

Just adding a little note to this thread as the suggestion I placed as feature request in SF.Net could work with this idea really perfectly!

https://xoops.org/modules/newbb/viewtopic.php?topic_id=46343&forum=8

This also means that the XOOPS Core Permission Configurator would be website sensitive and could also have a variable $sitegroups.

Hallo everyone!

OK, I found that there are also other ways to think about CORE Permissions system. I am bringing this here to have a debate. Folllowing are fundamental variations:

A. Concept of having modules and permissions linkage with groups

The modules would get and inherit the group properties and permissions would be assigned. There are disadvantages.

B. Concept of permissions quality (Unix type) defined and applied to modules based on vHost.

In this system, the absolute permission quality is defined from the beginning. Hence it starts from the site group or vHost related permissions where User = vHost!

Therefore all the permissions are then vHost/User related. I do not know if it makes sense to have User = vHost or if it would be better to have User = Admin, or Mr. X...

In this regards, I have placed a message here:

http://sourceforge.net/tracker/index.php?func=detail&aid=1417524&group_id=41586&atid=430843

Permission duplicate function
The Unix permissions based on User=vHost could be also duplicated and applied to groups.

Absolute permission structure
It would be really helpful to have groups and users individually have permissions. This could only be achieved if the permissions have an absolute quality. Only then they could be applied by a template to groups or users or even sites.

MOST IMPORTANT: The module developers would have NOTHING to do with the permissions. It is the CORE that controls and installs module permissions. There would be a standardized structure from the core. Thats my vision of Future Xoops!!!

I am interested to know what others think!