Skip to content

Commit 0462bb0

Browse files
committed
docs(admin): clarify dav:move-calendar --force behaviour
Without --force the command fails on name conflicts and incompatible group shares. With --force, group shares are dropped and a new name is tried up to ten times; fails if none are free. AI-Assisted-By: claude-sonnet-4-6 Signed-off-by: Anna Larch <anna@nextcloud.com>
1 parent c6c65cf commit 0462bb0

1 file changed

Lines changed: 9 additions & 3 deletions

File tree

admin_manual/occ_database.rst

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -116,9 +116,15 @@ Move a calendar from one user to another::
116116

117117
sudo -E -u www-data php occ dav:move-calendar personal layla fred
118118

119-
Use ``-f`` / ``--force`` to enforce the move when there are share
120-
conflicts. A unique name is generated automatically if there is a
121-
naming conflict at the destination.
119+
Without ``--force``, the command fails if the destination user already
120+
has a calendar with the same name, or if the calendar is shared with a
121+
group the destination user is not a member of.
122+
123+
Use ``-f`` / ``--force`` to proceed anyway: conflicting group shares are
124+
dropped, and if the calendar name is already taken at the destination a
125+
new name is tried automatically (``personal-1``, ``personal-2``, up to
126+
ten attempts). The command fails if no free name is found within those
127+
attempts.
122128

123129
dav:clear-calendar-unshares
124130
""""""""""""""""""""""""""""

0 commit comments

Comments
 (0)