Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multifilesystem & autocreation of calendars conflict #208

Closed
vuntz opened this issue Sep 15, 2014 · 0 comments · Fixed by #209
Closed

multifilesystem & autocreation of calendars conflict #208

vuntz opened this issue Sep 15, 2014 · 0 comments · Fixed by #209
Labels
Milestone

Comments

@vuntz
Copy link
Contributor

vuntz commented Sep 15, 2014

I'm trying to have a setup with multifilesystem and /$login/ as a collection. However, radicale currently creates /$login.props (due to the autocreation magic) and this makes radicale consider /$login/ a leaf, not a node (and therefore not a collection).

The only fix I can think of for that is to not automatically create .props files for multifilesystem.

vuntz added a commit to vuntz/Radicale that referenced this issue Sep 15, 2014
This is required as we do not want .props files to be created for nodes,
otherwise they'll stop being considered as nodes, which will break
discovery of calendars.

This fixes Kozea#208
vuntz added a commit to vuntz/Radicale that referenced this issue Sep 25, 2014
This is required as we do not want .props files to be created for nodes,
otherwise they'll stop being considered as nodes, which will break
discovery of calendars.

This fixes Kozea#208
@liZe liZe added this to the 1.0 milestone Oct 2, 2014
@liZe liZe added the bug label Oct 2, 2014
@liZe liZe closed this as completed in #209 Mar 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants