[Tickets #11438] Inconsistent behaviour of [share][hidden]

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/11438
------------------------------------------------------------------------------
  Ticket             | 11438
  Created By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Inconsistent behaviour of [share][hidden]
  Queue              | Kronolith
  Version            | Git master
  Type               | Bug
  State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Jan Schneider, Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2012-09-20 18:12) wrote:

When using dynamic view, and $conf[share][hidden] is set any calendars  
provided by the timeobjects API that are not backed by shares and  
"subscribed" to are hidden in the UI. I.e., it is impossible to select  
these for viewing.  When the timeobject is based on an actual share  
like an Address book that's fine since you can still "subscribe" to  
the share and have it appear, but if the timeobject provided via the  
API is not share based then it becomes impossible to ever see these  
calendars. For example, Whups provides timeobjects based on "My  
Tickets", not on individual shares and none of the objects provided by  
the timeobjects application is based on shares.

When viewing in the traditional view, the $conf[share][hidden] setting  
is ignored when building the list of available timeobject calendars.

So I think we need to:

(1) Fix the traditional view so that it honors the hidden setting.
(2) Add some new return value to the listTimeobjectsCategories API  
method that indicates whether or not the objects are share based and  
should be subject to filtering through the [share][hidden] setting.