Hello again everyone,
I'm still using infCloud and I'm starting to use the todo list feature.
The backend is radicale v0.10.
What I'm trying to do is moving an item from a todolist to another. To
do this, I start to edit an item and I then change the attached
collection. I then click on save.
infCloud starts by telling me the this is forbidden by a short red error
message that dissapear after one or two seconds. I can see the following
log message in radicale :
2015-04-15 11:17:53,170 - INFO: MOVE request at
As the message disappear and nothing else happens, I can click on save
once again. This time the item is correctly saved in the new collection,
but not deleted from the previous one. I can see the following log
message in radicale :
2015-04-15 11:18:03,233 - INFO: PUT request at
What I can infer is that infCloud has a sort of fallback mode that
replace the MOVE verb by a simple PUT. Could it be a bug in infCloud ?
Could it be radicale that does not support the MOVE verb ?
Thanks for your answer...
I'm using infCloud and I'm just sarting to use the todo list.
I'm surprised to see that todo list is not checked by default. Is it
normal ? Is it possible to make it checked by default ?
I'm not quite sure, but could it be that the very first time after
install/upgrade to 0.12.2 the "new appointment" dialog shows NANNANNAN for
time and date instead of the current/selected date?
I had some todo that was disappearing from my todo list.
I found some interesting informations in my browser's console :
unable to parse vTodo"
How can I check the reason of this parsing error ?
The item has been created by infCloud.
The backend is still radicale.
Other items are working perfectly.
In a previous mail (2015-01-14 @ 09:56), I was asking how to configure
radicale permissions in order to allow access and shared calendars used
by thunderbird, davdroid and caldavzap.
It is now working and I will tell you about my configuration.
This is what I wanted to do :
> With radicale v0.9
> How would configure the rights file in order to get the following
> behaviour :
> existing calendars :
> rights :
> - each user car read an write his own calendard
> - user1 can *read* user2/shared2 calendar
> - user2 car *read an write* user1/shared1 calendar
First, I have to tell that I was so desperate that tried everything.
Among those "everythings", I upgraded radicale to radicale v0.10.
Some settings or features might not work with previous versions.
Here is the content of my rights file :
[authenticated user can read root path]
[owner can write its collections]
[user1 can read user2]
[user1 can read and write user2/shared2]
[user2 can read user1 and user1/shared1]