I use CalDAVzap with a list of calendars. In my config.js, I have:
var globalCalendarSelected='jv/default/';
So I expect this calendar to be selected by default. However, CalDAVzap still selects the first available calendar instead.
This happens with FireFox and Chrome.
Do I misunderstand the purpose of globalCalendarSelected?
-- Johan
Hi Johan, send me url of calendar you want to have selected and i will check if 'jv/default' is correct form. Btw, do you have any calendar settings stored at server? Another possibility could be that your server settings rewrite your config.js
Regards, Andrej Lezo Dňa 2. 12. 2013 14:29 Johan Vromans wrote / napísal(a):
I use CalDAVzap with a list of calendars. In my config.js, I have:
var globalCalendarSelected='jv/default/';
So I expect this calendar to be selected by default. However, CalDAVzap still selects the first available calendar instead.
This happens with FireFox and Chrome.
Do I misunderstand the purpose of globalCalendarSelected?
-- Johan
Andrej Lezo andrej.lezo@inf-it.com writes:
Btw, do you have any calendar settings stored at server? Another possibility could be that your server settings rewrite your config.js
That is the clue...
In config,js:
var globalAccountSettings = [ { href: 'http://davical.squirrel.nl/caldav.php/jv/', ... settingsAccount: true, ... } ];
I deleted the settings records from the database (using psql :)) and now the problem is solved...
Is the setting of settingsAccount necessary? Useful?
-- Johan
It is useful for small intranet setups (without login screen) and without storing the settings on the server (settingsAccount: false), or for servers without support for custom properties.
JM
On 02 Dec 2013, at 05:00 pm, Johan Vromans jvromans@squirrel.nl wrote:
Andrej Lezo andrej.lezo@inf-it.com writes:
Btw, do you have any calendar settings stored at server? Another possibility could be that your server settings rewrite your config.js
That is the clue...
In config,js:
var globalAccountSettings = [ { href: 'http://davical.squirrel.nl/caldav.php/jv/', ... settingsAccount: true, ... } ];
I deleted the settings records from the database (using psql :)) and now the problem is solved...
Is the setting of settingsAccount necessary? Useful?
-- Johan
-
Andrej Lezo -
Johan Vromans -
Ján Máté