From 9d0439b9f8eaffddda959e2070baf8a9cd9db428 Mon Sep 17 00:00:00 2001 From: Dan Lister Date: Thu, 23 Oct 2025 09:59:20 +0100 Subject: [PATCH 1/3] Update FAQ with upgrade failure troubleshooting Added troubleshooting information for upgrade failures due to long file paths. --- .../resolve-issues-quickly-and-efficiently/faq.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md index 8a02846717a..5eaeb9d9b72 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md @@ -20,3 +20,13 @@ For the following scenarios you may find that deployments (and other operations) ## User: username@domain.net could not be authenticated at xxx This error usually mean that the user's account does not have the same user name and password on the environment you're deploying to. So when that user is deploying from development to staging they will get this error if they either don't exist on the staging environment or if their password is different between the dev and staging environment. + +## My project fails to upgrade (e.g. Standard → Pro) with build errors + +This can happen if your project contains very long file or folder paths (typically over 200 characters). During a plan upgrade, the deployment process may fail to find certain files, resulting in errors such as: + +``` +error CS0234: The type or namespace name 'X' does not exist in the namespace 'X' (are you missing an assembly reference?) +``` + +To fix, shorten the folder structure or rename long files so that the full file paths stay below 200 characters. Commit and push these changes, then try the upgrade again. From 394f818ee661125bdd983e0fcf24e97ebafecb08 Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Thu, 23 Oct 2025 13:42:11 +0200 Subject: [PATCH 2/3] Update umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md --- .../resolve-issues-quickly-and-efficiently/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md index 5eaeb9d9b72..16e397ef9e3 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md @@ -21,7 +21,7 @@ For the following scenarios you may find that deployments (and other operations) This error usually mean that the user's account does not have the same user name and password on the environment you're deploying to. So when that user is deploying from development to staging they will get this error if they either don't exist on the staging environment or if their password is different between the dev and staging environment. -## My project fails to upgrade (e.g. Standard → Pro) with build errors +## My project fails to upgrade (for example, Standard → Pro) with build errors This can happen if your project contains very long file or folder paths (typically over 200 characters). During a plan upgrade, the deployment process may fail to find certain files, resulting in errors such as: From 5abbef5935d7d6f9a29a3dc4f2002123b96d58ef Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Thu, 23 Oct 2025 13:42:18 +0200 Subject: [PATCH 3/3] Update umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md --- .../resolve-issues-quickly-and-efficiently/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md index 16e397ef9e3..5c49561eb46 100644 --- a/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md +++ b/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/faq.md @@ -23,7 +23,7 @@ This error usually mean that the user's account does not have the same user name ## My project fails to upgrade (for example, Standard → Pro) with build errors -This can happen if your project contains very long file or folder paths (typically over 200 characters). During a plan upgrade, the deployment process may fail to find certain files, resulting in errors such as: +This can happen if your project contains long file or folder paths (typically over 200 characters). During a plan upgrade, the deployment process may fail to find certain files, resulting in errors such as: ``` error CS0234: The type or namespace name 'X' does not exist in the namespace 'X' (are you missing an assembly reference?)