I have a category "Main" associated with a "Main" structure which I DO NOT want people to be able to comment on. I have another structure "TS" with its own category and I want people in the TS group to be able to comment on TS pages.
Current permission set up: I have global permissions set to grant comment posting and reading to all Registered Members.
I have permissions in the Main category set so that no one has permissions to post and read (registered is unchecked, and no groups are selected), yet everyone can still post and read comments in main.
If I remove global permissions for post and read, then no one can post and read in any category, even if I grant the group those permissions for their category.
I ran this by a member of the IRC and they said it sounded like a bug as well. I do believe that I am using the permissions correctly, and that I should be able to limit this permissions by removing it from the category permissions.
This is fixed in Tiki 8.
Prior to Tiki 8, comment permissions had a global scope, thus it was not possible to assign comment permissions per category. The interface gave the impression that this was possible. In Tiki 8 comment permissions are available at a category level, and it will fix this problem.
Tiki 8 will also fix the display issue for permissions and only show permissions that actually apply at a given level.
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.tikiwiki.org were not accepted. Please make sure you are using RSA keys. Thanks.
Unable to connect to show2.tikiwiki.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.tikiwiki.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.tikiwiki.org instance. To start, simply select a version and click on "Create show2.tikiwiki.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.tikiwiki.org.
The URL for the show2.tikiwiki.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.tikiwiki.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|