With Staging and Approval, you are required to setup a category for Staging, and one for Approval.
My site has other categories, lets call them A and B. I have things setup fairly tight so only people in group A can view/edit Category A content. I also want to restrict the approval process to only a few people in group C.
If someone in group A modifies a page in Category A, it gets assigned to the staging category.
<Enter the bug>
Once I Approve that change, the page now belongs to Category A AND the approval category. Since not all users have view/edit rights to the approval category, they are now unable to edit that page any further.
Ideally, I'd like to see it so an approval category isn't necessary, I just define a group (or groups) who can approve pages.
If the approval category is necessary, then it needs to be removed from the page once approved.
Does this problem still exist in Tiki 6? I did some testing in Tiki 6 (i.e. even though some users that have not edit rights to the approval category, they are able to to see the edit icons so long as there was a corresponding staging page in the staging category that they can edit. When they click on those icons, they get sent to edit the staging page.
They need at least view perms of course.
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|