From 633cb73e8cb3c4a359e9fa24910ac75879b2b32f Mon Sep 17 00:00:00 2001 From: Yornik Heyl Date: Thu, 2 Jul 2026 11:45:42 +0200 Subject: [PATCH 1/4] Add Atlas 2 note to custom error page how-to The custom error page how-to only documented the Atlas 3 location (theme/web/error_page). Atlas 2 apps treat the entire theme folder as the web root, so following the Atlas 3 path nests the error_page folder one level too deep and the pages are never served. Add the same Atlas 2 note already present in the Studio Pro 9 (howto9) version to the current and Studio Pro 10 (howto10) versions, directing Atlas 2 users to place error_page in the theme folder directly (or upgrade to Atlas 3). Co-Authored-By: Claude Opus 4.8 --- content/en/docs/howto/front-end/custom-error-page.md | 4 ++++ content/en/docs/howto10/front-end/custom-error-page.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/content/en/docs/howto/front-end/custom-error-page.md b/content/en/docs/howto/front-end/custom-error-page.md index ff6bfd24b91..aa20378d955 100644 --- a/content/en/docs/howto/front-end/custom-error-page.md +++ b/content/en/docs/howto/front-end/custom-error-page.md @@ -41,6 +41,10 @@ Before starting this how-to, make sure you have completed the following prerequi ## Creating a Custom Error Page {#create-custom-error} +{{% alert color="info" %}} +If you are using Atlas 2, consider [upgrading](/refguide9/moving-from-atlas-2-to-3/). If you cannot, follow the instructions below but create the **error_page** folder in your **theme** folder directly. +{{% /alert %}} + If you are using Atlas 3, do the following: 1. Open the local folder of your app. diff --git a/content/en/docs/howto10/front-end/custom-error-page.md b/content/en/docs/howto10/front-end/custom-error-page.md index d2301fa22e5..2aa5a6bb9f8 100644 --- a/content/en/docs/howto10/front-end/custom-error-page.md +++ b/content/en/docs/howto10/front-end/custom-error-page.md @@ -41,6 +41,10 @@ Before starting this how-to, make sure you have completed the following prerequi ## Creating a Custom Error Page {#create-custom-error} +{{% alert color="info" %}} +If you are using Atlas 2, consider [upgrading](/refguide9/moving-from-atlas-2-to-3/). If you cannot, follow the instructions below but create the **error_page** folder in your **theme** folder directly. +{{% /alert %}} + If you are using Atlas 3, do the following: 1. Open the local folder of your app. From 14753d8b87da9157350240c8edb7c5be40d424fb Mon Sep 17 00:00:00 2001 From: Yornik Heyl Date: Thu, 2 Jul 2026 11:56:09 +0200 Subject: [PATCH 2/4] Clarify Atlas 2 note wording and scope to Mendix 9 Reword the Atlas 2 note so it reads as guidance for readers who land on the page regardless of their version. Atlas 2 only applies to supported Mendix 9 apps still on Atlas 2 (Mendix 10 and 11 use Atlas 3+), so the note now states this explicitly rather than implying Atlas 2 is a general option. Co-Authored-By: Claude Opus 4.8 --- content/en/docs/howto/front-end/custom-error-page.md | 2 +- content/en/docs/howto10/front-end/custom-error-page.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/howto/front-end/custom-error-page.md b/content/en/docs/howto/front-end/custom-error-page.md index aa20378d955..2e94f1a468d 100644 --- a/content/en/docs/howto/front-end/custom-error-page.md +++ b/content/en/docs/howto/front-end/custom-error-page.md @@ -42,7 +42,7 @@ Before starting this how-to, make sure you have completed the following prerequi ## Creating a Custom Error Page {#create-custom-error} {{% alert color="info" %}} -If you are using Atlas 2, consider [upgrading](/refguide9/moving-from-atlas-2-to-3/). If you cannot, follow the instructions below but create the **error_page** folder in your **theme** folder directly. +These steps apply to Atlas 3, which is used from Mendix 9 onwards. If you are on Mendix 9 and your app still uses **Atlas 2**, the folder structure is different: the entire **theme** folder acts as the web root. In that case, create the **error_page** folder directly inside **theme** (not inside **theme/web**), otherwise it is nested one level too deep in the deployment package and the custom error pages are not served. Alternatively, [upgrade the app to Atlas 3](/refguide9/moving-from-atlas-2-to-3/). {{% /alert %}} If you are using Atlas 3, do the following: diff --git a/content/en/docs/howto10/front-end/custom-error-page.md b/content/en/docs/howto10/front-end/custom-error-page.md index 2aa5a6bb9f8..fe918d2c1de 100644 --- a/content/en/docs/howto10/front-end/custom-error-page.md +++ b/content/en/docs/howto10/front-end/custom-error-page.md @@ -42,7 +42,7 @@ Before starting this how-to, make sure you have completed the following prerequi ## Creating a Custom Error Page {#create-custom-error} {{% alert color="info" %}} -If you are using Atlas 2, consider [upgrading](/refguide9/moving-from-atlas-2-to-3/). If you cannot, follow the instructions below but create the **error_page** folder in your **theme** folder directly. +These steps apply to Atlas 3, which is used from Mendix 9 onwards. If you are on Mendix 9 and your app still uses **Atlas 2**, the folder structure is different: the entire **theme** folder acts as the web root. In that case, create the **error_page** folder directly inside **theme** (not inside **theme/web**), otherwise it is nested one level too deep in the deployment package and the custom error pages are not served. Alternatively, [upgrade the app to Atlas 3](/refguide9/moving-from-atlas-2-to-3/). {{% /alert %}} If you are using Atlas 3, do the following: From 77b893b6cec4510e5bce6427fe9e9a068bdf06e5 Mon Sep 17 00:00:00 2001 From: ConnorLand <47385345+ConnorLand@users.noreply.github.com> Date: Fri, 3 Jul 2026 14:28:52 +0200 Subject: [PATCH 3/4] Update custom-error-page.md --- content/en/docs/howto/front-end/custom-error-page.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/howto/front-end/custom-error-page.md b/content/en/docs/howto/front-end/custom-error-page.md index 2e94f1a468d..b91b386b5a8 100644 --- a/content/en/docs/howto/front-end/custom-error-page.md +++ b/content/en/docs/howto/front-end/custom-error-page.md @@ -42,7 +42,7 @@ Before starting this how-to, make sure you have completed the following prerequi ## Creating a Custom Error Page {#create-custom-error} {{% alert color="info" %}} -These steps apply to Atlas 3, which is used from Mendix 9 onwards. If you are on Mendix 9 and your app still uses **Atlas 2**, the folder structure is different: the entire **theme** folder acts as the web root. In that case, create the **error_page** folder directly inside **theme** (not inside **theme/web**), otherwise it is nested one level too deep in the deployment package and the custom error pages are not served. Alternatively, [upgrade the app to Atlas 3](/refguide9/moving-from-atlas-2-to-3/). +These steps apply to Atlas 3, which is used from Mendix 9 and above. If you are on Mendix 9 and your app still uses **Atlas 2**, the folder structure is different: the entire **theme** folder acts as the web root. In that case, create the **error_page** folder directly inside **theme** (not inside **theme/web**), otherwise it is nested one level too deep in the deployment package and the custom error pages are not served. Alternatively, [upgrade the app to Atlas 3](/refguide9/moving-from-atlas-2-to-3/). {{% /alert %}} If you are using Atlas 3, do the following: From 63b9c5447781d425b09f9cc2a226342e14da05f0 Mon Sep 17 00:00:00 2001 From: ConnorLand <47385345+ConnorLand@users.noreply.github.com> Date: Fri, 3 Jul 2026 14:29:14 +0200 Subject: [PATCH 4/4] Update custom-error-page.md --- content/en/docs/howto10/front-end/custom-error-page.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/howto10/front-end/custom-error-page.md b/content/en/docs/howto10/front-end/custom-error-page.md index fe918d2c1de..587da4b2a12 100644 --- a/content/en/docs/howto10/front-end/custom-error-page.md +++ b/content/en/docs/howto10/front-end/custom-error-page.md @@ -42,7 +42,7 @@ Before starting this how-to, make sure you have completed the following prerequi ## Creating a Custom Error Page {#create-custom-error} {{% alert color="info" %}} -These steps apply to Atlas 3, which is used from Mendix 9 onwards. If you are on Mendix 9 and your app still uses **Atlas 2**, the folder structure is different: the entire **theme** folder acts as the web root. In that case, create the **error_page** folder directly inside **theme** (not inside **theme/web**), otherwise it is nested one level too deep in the deployment package and the custom error pages are not served. Alternatively, [upgrade the app to Atlas 3](/refguide9/moving-from-atlas-2-to-3/). +These steps apply to Atlas 3, which is used from Mendix 9 and above. If you are on Mendix 9 and your app still uses **Atlas 2**, the folder structure is different: the entire **theme** folder acts as the web root. In that case, create the **error_page** folder directly inside **theme** (not inside **theme/web**), otherwise it is nested one level too deep in the deployment package and the custom error pages are not served. Alternatively, [upgrade the app to Atlas 3](/refguide9/moving-from-atlas-2-to-3/). {{% /alert %}} If you are using Atlas 3, do the following: