Merge pull request #13788 from nextcloud/jtr/refactor-calendar-troubleshooting

refactor: Move legacy contacts troubleshooting entry to Groupware

Author: joshtrichards

admin_manual/groupware/troubleshooting.rst

@@ -5,37 +5,52 @@ Troubleshooting
 ===============
 
 Calendar
-########
+--------
 
 Missing Shared Calendars
-************************
+^^^^^^^^^^^^^^^^^^^^^^^^
 
 **Problem:**
-    User should have access to a shared calendar, but the calendar is not displayed in Nextcloud Calendar or other CalDAV clients (e.g., DAVx⁵ or Thunderbird).
+    A user should have access to a shared calendar, but the calendar is not displayed in Nextcloud Calendar or other CalDAV clients (e.g., DAVx⁵ or Thunderbird).
 
 **Affected Versions:**
     - Nextcloud Server 31.0.5 and below
     - Nextcloud Server 30.0.11 and below
 
 **Possible Reason:**
-   A bug in previous versions of Nextcloud Server could mistakenly add a calendar unshare instead of removing the share permission. For example, a user has read access through a group membership, and the owner grants permission to a single user to modify a calendar. When removing the modify permission again, the unshare record was created.
+    A bug in previous versions of Nextcloud Server could mistakenly add a calendar unshare instead of removing the share permission. For example, a user has read access through a group membership, and the owner grants permission to a single user to modify a calendar. When the modify permission is removed, an unshare record is incorrectly created.
 
 **Troubleshooting Steps:**
 
 1. **Check for Hidden Calendars:**
-    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.
+    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 it is, check the box in front of the calendar to enable it again.
 
 2. **List Calendar Shares:**
-    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:
+    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 such a line exists, but the user should have access, you have three options:
 
 A. **Create a User Share and Remove It Again:**
     In most cases, sharing the calendar with the user again (as an individual/user share) will correct the state in the database.
 
 B. **Remove All Calendar Unshares for a User:**
-    ``occ dav:clear-calendar-unshares <uid>``.
+    Run ``occ dav:clear-calendar-unshares <uid>``.
 
 C. **Delete Specific Unshares:**
-    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.
+    Some users may have many calendar unshares, so it might be easier to delete only the unwanted unshare. The ``Share Id`` refers to the ID of a row in the ``oc_dav_shares`` database table. Delete the row with the matching ID to remove the unshare.
 
-**Why Isn't there an Automated Migration to Correct the Problem?**
-    Unsharing a calendar is a feature, and with the given information, we cannot determine if a calendar was unshared on purpose or as a result of the bug.
+**Why isn't there an automated migration to correct the problem?**
+    Unsharing a calendar is a feature, and with the given information, we cannot determine if a calendar was unshared intentionally or as a result of the bug.
+
+Contacts
+--------
+
+Unable to update contacts or events
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+If you get an error like:
+
+``PATCH https://example.com/remote.php/dav HTTP/1.0 501 Not Implemented``
+
+it is likely because of a misconfigured web server:
+
+    Your web server is misconfigured and blocks the required DAV methods.
+    Please refer to :ref:`trouble-webdav-label` for troubleshooting steps.

admin_manual/issues/general_troubleshooting.rst

@@ -374,25 +374,6 @@ Troubleshooting contacts & calendar
 .. tip::
   Please also refer to the troubleshooting article in the groupware section: :ref:`troubleshooting_groupware`.
 
-Unable to update contacts or events
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-If you get an error like:
-
-``PATCH https://example.com/remote.php/dav HTTP/1.0 501 Not Implemented``
-
-it is likely caused by one of the following reasons:
-
-Using Pound reverse-proxy/load balancer
-  As of writing this Pound doesn't support the HTTP/1.1 verb.
-  Pound is easily `patched
-  <http://www.apsis.ch/pound/pound_list/archive/2013/2013-08/1377264673000>`_
-  to support HTTP/1.1.
-
-Misconfigured Web server
-  Your Web server is misconfigured and blocks the needed DAV methods.
-  Please refer to :ref:`trouble-webdav-label` above for troubleshooting steps.
-
 Troubleshooting data-directory
 ------------------------------