Imagine a simple group setup in which we have an Employee group and a Manager group. Every manager is an employee and so has all of the permissions of an employee, so we make the Manager group inherit from the Employee group. We put the basic permissions on Employee, and the special permissions of managers on the Manager group. Good so far. Now we'd like to have a newsletter BossNews for managers, so naturally we subscribe the Manager group to the BossNews newsletter. But by the current group subscription rule, this automatically sends BossNews to the Employee group as well. Presumably not what we want, as the BossNews is intended to have the inside scoop that only Managers should see.
Since the inheritor group generally corresponds to a subset of the inherited group, it is very unlikely that the current rule will be useful — subscribing the subset to the newsletter should not automatically pull in the larger set.
Even reversing the newsletter subscription inheritance — so that subscribing Employee to a group automatically subscribes Manager — may be problematic. The subgroup may not want to see the "chatter" of the larger group. Think BoardOfDirectors as a subgroup of Managers — they probably do not want to see all of the Employee updates.
So I would recommend no inheritance at all for group subscriptions to newsletters, since you can always subscribe both Employee and Manager to a newsletter if that's who should receive the messages.
Right now, I can only get around this by having each member in two groups, one that via inheritance gets the correct permissions, and one that has no inheritance and gets the correct newsletters. This is a significant maintenance headache, as all group assignments must be done in duplicate. Note the list of members of one of these groups for privileges and the corresponding one for newsletters are identical, but I have to keep them that way by hand.
A better solution, which I respectfully request the TikiWiki maintainers implement, is simply to eliminate inheritance in group subscription to newsletters: when you subscribe a group, only direct members of that group are subscribed. If there is an upgrade script, it could automatically adjust group subscriptions across the upgrade to replicate the old behavior in the new scheme. Thanks for considering this change.
Show.tiki.org snapshot creation is in progress... Please monitor http:///snapshots/ for progress. Note that if you get a popup asking for a username/password, please just enter "show" and "show".
Password reset was successful
Password reset failed
Show.tiki.org instance destruction is in progress... Please wait...
The public/private keys configured to connect to show2.tiki.org were not accepted. Please make sure you are using RSA keys. Thanks.
Unable to connect to show2.tiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is currently under maintenance. Sorry for the inconvenience.
Unable to get information from show2.tiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is in the progress of creating the new instance. Please continue waiting for a minute or two. If this continues on for more than 10 minutes, please let us know of the problem so that we can do something about it. Thanks.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
The URL for the show2.tiki.org instance that demonstrates this bug is at: http://. Note that if you get a popup asking for a username/password, please just enter "show" and "show". This is different from the initial login and password for a new Tiki which is "admin" and "admin".
For the install log, see http:///info.txt
Note that if you see PHP errors or a Tiki claiming to be missing third party software, the instance creation is probably not finished. Please wait a couple minutes and reload.
Snapshots are database dumps of the configuration that developers can download for debugging. Once you have reproduced your bug on the show2.tiki.org instance, create a snapshot that can then be downloaded by developers for further investigation.
Snapshots can be accessed at: http:///snapshots/. Note that if you get a popup asking for a username/password, please just enter "show" and "show".Create new snapshot
|No attachments for this item|