Hi, You're right, sorry for double email. I reply on ML to publish the solution to the world :) Thank you very much for that ! Cheers, Bastien Sevajol. On 26/07/2016 18:10, Ján Máté wrote: > Hi, > > > Use the following patch (which ensures that if only > globalAccountSettings option is used, then all calendars are loaded): > > https://www.inf-it.com/fixes/main.js-loadall.diff > > After applying the patch you must execute the cache_update.sh (to > force clients to reload the changed source code from your server). > > > Cheers, > > > JM > > > p.s.: the patch will be included in the next version ... > > > >> On 26 Jul 2016, at 12:06, Bastien Sevajol &lt;bastien.sevajol(a)algoo.fr >> <mailto:bastien.sevajol@algoo.fr>> wrote: >> >> Hi, >> I just sent this email to caldavzap(a)inf-it.com, but >> davclients(a)inf-it.com is maybe more appropriate ? >> >> Thank you for your CalDavZap application. I think is the only free >> full javascript caldav client on the web :) >> I have a problem with calendar configuration. I configure 3 calendars >> in globalAccountSettings, but only one is visible in interface. >> config.js globalAccountSettings is: >>> >>> var globalAccountSettings=[ >>> { >>> href: 'http://127.0.0.1:5232/user/3.ics/', >>> userAuth: >>> { >>> userName: &#x27;bastien.sevajol(a)algoo.fr&#x27;o.fr', >>> userPassword: &#x27;bastien.sevajol(a)algoo.fr&#x27; >>> }, >>> timeOut: 90000, >>> lockTimeOut: 10000, >>> checkContentType: true, >>> settingsAccount: true, >>> delegation: true, >>> hrefLabel: 'http://127.0.0.1:5232/user/3.ics/', >>> forceReadOnly: null, >>> ignoreAlarms: false, >>> backgroundCalendars: [] >>> }, >>> { >>> href: 'http://127.0.0.1:5232/workspace/2.ics/', >>> userAuth: >>> { >>> userName: &#x27;bastien.sevajol(a)algoo.fr&#x27;o.fr', >>> userPassword: &#x27;bastien.sevajol(a)algoo.fr&#x27; >>> }, >>> timeOut: 90000, >>> lockTimeOut: 10000, >>> checkContentType: true, >>> settingsAccount: true, >>> delegation: true, >>> hrefLabel: 'http://127.0.0.1:5232/workspace/2.ics/', >>> forceReadOnly: null, >>> ignoreAlarms: false, >>> backgroundCalendars: [] >>> }, >>> { >>> href: 'http://127.0.0.1:5232/workspace/1.ics/', >>> userAuth: >>> { >>> userName: &#x27;bastien.sevajol(a)algoo.fr&#x27;o.fr', >>> userPassword: &#x27;bastien.sevajol(a)algoo.fr&#x27; >>> }, >>> timeOut: 90000, >>> lockTimeOut: 10000, >>> checkContentType: true, >>> settingsAccount: true, >>> delegation: true, >>> hrefLabel: 'http://127.0.0.1:5232/workspace/1.ics/', >>> forceReadOnly: null, >>> ignoreAlarms: false, >>> backgroundCalendars: [] >>> }, >>> ]; >> <Mail Attachment.png> >> Actually, 2 others calendars are loaded and in HTML DOM, but with >> style="display: none;". >> Do you know this issue ? >> >> Thank's very much, >> Bastien Sevajol. >

Hi, After apply the path and execute cache_update.sh, i have similar behaviour: With these 3 configured calendars: I have only two calendar displayed (/user/1.ics/ and /workspace/2.ics/). Log says 3 calendar are reads: I can setup more calendars configs, bahaviour still like that. I you need more trace/information, i'm listening. Regards, Bastien Sevajol. On 26/07/2016 18:10, Ján Máté 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. On 28/07/2016 17:27, Ján Máté wrote:

Hi, You got it. After update globalAccountSettings as you say all works fine. Thak's for your help, Regards, Bastien. On 29/07/2016 10:33, Ján Máté wrote: