Make properties method return only properties the user can search. See: https://sourceforge.net/p/roundup/mailman/roundup-devel/thread/20170405002844.2004B80690%40vm71.cs.umb.edu/#msg35769250 [Roundup-devel] Bug in context/properties, lists properties user can't search. The HTMLClass::properties() method returns a list of all properties. This is used when creating sort on/group by filters on index pages. However somewhere in the code, a user needs search permission on the property in order for it to be used for grouping or sorting. This means the user can choose to sort/group an index page by a property that they have no search permission for. As a result the sort/group is ignored. This is confusing. I have changed the properties method to only return properties the user has View/Search permissions on. I also added a new cansearch argument set by default to True. If set to False, all properties regardless of Search permission are returned. Doc updated to include the new default operation and mention the use of cansearch argument.

--- a/CHANGES.txt	Wed Apr 05 21:20:20 2017 -0400
+++ b/CHANGES.txt	Wed Apr 05 21:38:32 2017 -0400
@@ -413,6 +413,11 @@
   will not add the arg to the url. In the example above @queryname
   will only be in the url if dispname is set in the request.
   (John Rouillard)
+- The HTMLClass::properties() method produced a list of properties
+  that the user could not search. As a result these properties can not
+  be used for sorting or grouping index pages. This patch eliminates
+  the confusion that results from this mismatch by verifying that all
+  properties returned are searchable. (John Rouillard)
 
 2016-01-11: 1.5.1