Hi,

documentation in config.js says:

// - href
//   Depending on the setup type set the value to:
//   a.) globalAccountSettings: full "principal URL"
//   b.) globalNetworkCheckSettings: "principal URL" WITHOUT the "USER/" part
//   c.) globalNetworkAccountSettings: "full URL" to the "auth" directory
...

...

...

// What is a "principal URL"? => Check you server documentation!

//   - "principal URL" is NOT "collection URL"

In your example below you use "collection URL" (calendar URL). Our software automatically

detects all collections for a given principal, you CANNOT use "collection URL" as a href value.

Correct principal URLs in your case are:

http://127.0.0.1:5232/user/

http://127.0.0.1:5232/workspace/

JM

On 29 Jul 2016, at 10:08, Bastien Sevajol <bastien.sevajol@algoo.fr> wrote:

Hi,

Sorry for multiple email. I will be more concise.

It not seems cache problem. Tested with multiple ways:
- Fresh web browser install 
- Deletion of all cache in browser
- With setup of apache2 config/.htaccess as said
Same behaviour, not all calendars are displayed.

I attach in this mail (or available at http://sk.bux.fr/~bux/caldavzap/2016-07-29/):
- config.js 
- a log of browser output (we can see an clear cache event)
- screenshot of interface with two calendar instead of 5.

Notice calendars urls are:
- http://127.0.0.1:5232/user/1.ics/
- http://127.0.0.1:5232/workspace/2ics/
- http://127.0.0.1:5232/workspace/1.ics/
- http://127.0.0.1:5232/workspace/3.ics/
- http://127.0.0.1:5232/workspace/4.ics/
and displayed calendars are:
- http://127.0.0.1:5232/user/1.ics/
- http://127.0.0.1:5232/workspace/4.ics/
maybe the "/workspace/" common structure of calendars is a problem for caldavzap ?

Regards,
Bastien.