From b54ee59e5210b9f7d9b8909b21f10a636a79afb5 Mon Sep 17 00:00:00 2001 From: Abdulaziz <60339265+Abdjulaziz@users.noreply.github.com> Date: Sun, 20 Oct 2024 22:20:30 +0200 Subject: [PATCH 1/3] Update path-too-long-exception.md Changed database query to show media items longer than 80 characters. Previous query showed all media now you only get the media you need to edit. --- .../deployments/path-too-long-exception.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/umbraco-cloud/troubleshooting/deployments/path-too-long-exception.md b/umbraco-cloud/troubleshooting/deployments/path-too-long-exception.md index 54bf40eccf8..3c2e93e7fc6 100644 --- a/umbraco-cloud/troubleshooting/deployments/path-too-long-exception.md +++ b/umbraco-cloud/troubleshooting/deployments/path-too-long-exception.md @@ -55,12 +55,13 @@ In order to fix this error, you will need to connect to the Live Environments pr ```sql - SELECT TOP (2000) [id] - ,[path], - Len(path) As valueLength + SELECT TOP (2000) [id], + [path], + LEN(path) AS valueLength FROM [dbo].[umbracoMediaVersion] - WHERE path IS NOT null - ORDER BY Len(path) DESC + WHERE LEN(path) > 80 + AND path IS NOT NULL + ORDER BY LEN(path) DESC; ``` 3. Identify the files with a path longer than 80 characters. 4. Find the files in the Media section in the Umbraco backoffice. From 2cf641da5d56c0940c3099cd90d7853bac957943 Mon Sep 17 00:00:00 2001 From: Abdulaziz <60339265+Abdjulaziz@users.noreply.github.com> Date: Mon, 21 Oct 2024 11:46:31 +0200 Subject: [PATCH 2/3] Update path-too-long-exception.md smal edit - no further changes needed --- .../troubleshooting/deployments/path-too-long-exception.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/umbraco-cloud/troubleshooting/deployments/path-too-long-exception.md b/umbraco-cloud/troubleshooting/deployments/path-too-long-exception.md index 3c2e93e7fc6..3c64f7adb31 100644 --- a/umbraco-cloud/troubleshooting/deployments/path-too-long-exception.md +++ b/umbraco-cloud/troubleshooting/deployments/path-too-long-exception.md @@ -63,11 +63,10 @@ In order to fix this error, you will need to connect to the Live Environments pr AND path IS NOT NULL ORDER BY LEN(path) DESC; ``` -3. Identify the files with a path longer than 80 characters. -4. Find the files in the Media section in the Umbraco backoffice. -5. Remove the media files from the backoffice. +3. Find the files in the Media section in the Umbraco backoffice. +4. Remove the media files from the backoffice. * Make sure to note down where the media item is being used in the content -6. Change the names of the media files giving them shorter names. +6. Change the names of the media files giving them a name less than 80 characters. 7. Re-upload the renamed file to the Media section in the backoffice. Once re-added in the backoffice, make sure to add the media back in the content where it was used. From 77887989a56fdc09fda9cb3c6310b4f8cf653eb0 Mon Sep 17 00:00:00 2001 From: sofietoft Date: Tue, 22 Oct 2024 12:20:40 +0200 Subject: [PATCH 3/3] Apply suggestions from code review --- .../troubleshooting/deployments/path-too-long-exception.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/umbraco-cloud/troubleshooting/deployments/path-too-long-exception.md b/umbraco-cloud/troubleshooting/deployments/path-too-long-exception.md index 3c64f7adb31..d51fb315714 100644 --- a/umbraco-cloud/troubleshooting/deployments/path-too-long-exception.md +++ b/umbraco-cloud/troubleshooting/deployments/path-too-long-exception.md @@ -66,7 +66,7 @@ In order to fix this error, you will need to connect to the Live Environments pr 3. Find the files in the Media section in the Umbraco backoffice. 4. Remove the media files from the backoffice. * Make sure to note down where the media item is being used in the content -6. Change the names of the media files giving them a name less than 80 characters. +6. Change the names of the media files giving them a name shorter than 80 characters. 7. Re-upload the renamed file to the Media section in the backoffice. Once re-added in the backoffice, make sure to add the media back in the content where it was used.