Hi All, I just found the config.js setting "globalSubscribedCalendars". I understand this feature as an option to add external calendar files to every user who has an account and can login with CalDavZap. I tried this setting here: var globalSubscribedCalendars={hrefLabel: 'Subscribed', calendars: [{displayName: 'Subscribed Calendar', href: 'http://www.schulferien.org/iCal/Ferien/icals/Ferien_Bayern_2015.ics', userAuth: {userName: '', userPassword: ''}, ignoreAlarm: true, color: '#ff0000', typeList: ['vevent','vtodo']}]}; But nothing changed and this calendar does not show up. Did understand this feature wrong? If possible, also explain the delegation/shared calendar feature mentioned in the description of globalSubscribedCalendars. Thanks Konrad
Hi Konrad,
On 06 Dec 2014, at 17:12, forum.news@gmx.de wrote:
Hi All,
I just found the config.js setting "globalSubscribedCalendars". I understand this feature as an option to add external calendar files to every user who has an account and can login with CalDavZap. I tried this setting here:
var globalSubscribedCalendars={hrefLabel: 'Subscribed', calendars: [{displayName: 'Subscribed Calendar', href: 'http://www.schulferien.org/iCal/Ferien/icals/Ferien_Bayern_2015.ics' <http://www.schulferien.org/iCal/Ferien/icals/Ferien_Bayern_2015.ics'>, userAuth: {userName: '', userPassword: ''}, ignoreAlarm: true, color: '#ff0000', typeList: ['vevent','vtodo']}]};
But nothing changed and this calendar does not show up.
Did understand this feature wrong?
it will work as as soon as the remote server will send proper CORS headers (because JavaScript makes a cross-domain request to a remote server where the ICS file is hosted) ...
If possible, also explain the delegation/shared calendar feature mentioned in the description of globalSubscribedCalendars.
Delegation is a server functionality (calendar-proxy-read and calendar-proxy-write support), shared calendars is used to load an ICS file from a remote server (read-only mode and the remote server must send proper CORS headers /JavaScript limitation/). JM
Thanks Konrad
Hi, I was able to figure out the problem with the globalSubscribedCalendars setting. I do use https and the subscribed calendar was http. This was the problem... Now it is working ;-). Still do not understand the delegation feature, though. What I wanted to do in the frist place is that CalDavZap shows a calender from my own calendar server from another user where my user has read access as well. Should this work or not if the server (Radicale) is configured correctly? Thanks Konrad Am 06.12.2014 um 17:35 schrieb Ján Máté:
Hi Konrad,
On 06 Dec 2014, at 17:12, forum.news@gmx.de <mailto:forum.news@gmx.de> wrote:
Hi All,
I just found the config.js setting "globalSubscribedCalendars". I understand this feature as an option to add external calendar files to every user who has an account and can login with CalDavZap. I tried this setting here:
var globalSubscribedCalendars={hrefLabel: 'Subscribed', calendars: [{displayName: 'Subscribed Calendar', href: 'http://www.schulferien.org/iCal/Ferien/icals/Ferien_Bayern_2015.ics' <http://www.schulferien.org/iCal/Ferien/icals/Ferien_Bayern_2015.ics%27>, userAuth: {userName: '', userPassword: ''}, ignoreAlarm: true, color: '#ff0000', typeList: ['vevent','vtodo']}]};
But nothing changed and this calendar does not show up.
Did understand this feature wrong?
it will work as as soon as the remote server will send proper CORS headers (because JavaScript makes a cross-domain request to a remote server where the ICS file is hosted) ...
If possible, also explain the delegation/shared calendar feature mentioned in the description of globalSubscribedCalendars.
Delegation is a server functionality (calendar-proxy-read and calendar-proxy-write support), shared calendars is used to load an ICS file from a remote server (read-only mode and the remote server must send proper CORS headers /JavaScript limitation/).
JM
Thanks Konrad
Hi,
On 06 Dec 2014, at 19:21, forum.news@gmx.de wrote:
Hi,
I was able to figure out the problem with the globalSubscribedCalendars setting. I do use https and the subscribed calendar was http. This was the problem... Now it is working ;-).
Still do not understand the delegation feature, though.
What I wanted to do in the frist place is that CalDavZap shows a calender from my own calendar server from another user where my user has read access as well. Should this work or not if the server (Radicale) is configured correctly?
then the delegation functionality (calendar-proxy-read and calendar-proxy-write) is what you need (see http://svn.calendarserver.org/repository/calendarserver/CalendarServer/trunk... <http://svn.calendarserver.org/repository/calendarserver/CalendarServer/trunk/doc/Extensions/caldav-proxy.txt> ). CalDavZAP supports this feature, but it must be supported also on server side. If your server supports it (and you have set proper principal/collection privileges) then it works automatically (DAViCal, Calendarserver, ...). Check our CalDavZAP demo (https://www.inf-it.com/caldavzap/ <https://www.inf-it.com/caldavzap/> ) and click to the right icon at the top of the resource list => you will see the "inf-it.com/debug" principal with 2 calendars (this is the delegation functionality). JM
Thanks Konrad
participants (2)
-
forum.news＠gmx.de -
Ján Máté