Whilst the various .tpl files associated with search do a check on the $prefs.feature_XXX when showing the drop down menu for refining the search there is no check on whether the individual user has the privilege to use the feature. Therefore menu options can be shown that are not appropriate.
Also the drop down menus are slightly different for the three different .tpls files
No longer relevant - 15th June 2013
updated and attached as proposed patch
-- -- -- -- -- -- -- ---
I do not agree with the test about permission as a general solution.
For instance - tiki_p_view can not be set globally, but some pages can have special permissions.
Perhaps we need a global setting. But this is not general at all.
Otherwise I agree with the missing tracker - and calendar options. I committed it. Thanks
doh! yep you are right this isn't a general solution - I guess I have been steered by my own use of tiki where I avoid using individual permissions and actually I don't let clients/users do that except where it is unavoidable. Instead I always try to use Categories that implement an agreed security policy (for access control that is).
On balance I think the patch could suit some users since showing Feature buttons that the user may not even know about, may be a 'greater problem' than missing some items in a search that have had their permissions individually set.
Need to think harder though since a generic solution should probably still not show the Feature buttons but should include individually 'permitted' items. hmmm tricky!
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