Skip to content

Commit c0b1a84

Browse files
authored
Merge pull request #13154 from nextcloud/backport/13151/stable31
[stable31] docs(groupware): update troubleshooting article for missing calendars
2 parents 8827902 + 2b80ee8 commit c0b1a84

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

admin_manual/groupware/troubleshooting.rst

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,12 +26,15 @@ Missing Shared Calendars
2626
It's possible for a user to hide a calendar. Please check in Nextcloud Calendar if the missing calendar is listed in the "hidden" section. If the missing calendar is listed there, check the box in front of the calendar to enable it again.
2727

2828
2. **List Calendar Shares:**
29-
Run the command ``occ dav:list-calendar-shares <uid>`` to list all shares for a user. Look for lines with the Calendar URI/Calendar Name of the missing calendar and Permissions = Unshare. If there's such a line, but the user should have access, you have two options:
29+
Run the command ``occ dav:list-calendar-shares <uid>`` to list all shares for a user. Look for lines with the Calendar URI/Calendar Name of the missing calendar and Permissions = Unshare. If there's such a line, but the user should have access, you have three options:
3030

31-
A. **Remove All Calendar Unshares for a User:**
31+
A. **Create a User Share and Remove It Again:**
32+
In most cases, sharing the calendar with the user again (as an individual/user share) will correct the state in the database.
33+
34+
B. **Remove All Calendar Unshares for a User:**
3235
``occ dav:clear-calendar-unshares <uid>``.
3336

34-
B. **Delete Specific Unshares:**
37+
C. **Delete Specific Unshares:**
3538
Some users may have many calendar unshares, so it might be easier to delete only the unwanted unshare. The ``Share Id`` references the id of a row in the ``oc_dav_shares`` database table. Delete the row with the matching id to remove the unshare.
3639

3740
**Why Isn't there an Automated Migration to Correct the Problem?**

0 commit comments

Comments
 (0)