From 794bb5ade86dbf49fdee9185571d72f0ea5d6f2c Mon Sep 17 00:00:00 2001 From: Erik-Jan Westendorp Date: Mon, 4 Mar 2024 15:59:40 +0100 Subject: [PATCH 1/3] Remove simple --- 13/umbraco-cms/tutorials/custom-error-page.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/13/umbraco-cms/tutorials/custom-error-page.md b/13/umbraco-cms/tutorials/custom-error-page.md index 4536a08e510..1f4c96fc938 100644 --- a/13/umbraco-cms/tutorials/custom-error-page.md +++ b/13/umbraco-cms/tutorials/custom-error-page.md @@ -204,7 +204,7 @@ To **test this locally**, in Visual Studio replace `app.UseDeveloperExceptionPag #### Trigger a 500 error -You can trigger a simple 500 error on your frontend by changing a Model.Value property in your template. For example, on a document type with a property called `test`. The way to render it in the frontend would be `Model.Value("test");` To trigger a 500 error page you can add anything after Value such as `Model.ValueTest("test");` +You can trigger a 500 error on your frontend by changing a Model.Value property in your template. For example, on a document type with a property called `test`. The way to render it in the frontend would be `Model.Value("test");` To trigger a 500 error page you can add anything after Value such as `Model.ValueTest("test");` ## Maintenance Page From f202d1ce40461271a79fdd1084cc2af9968673f3 Mon Sep 17 00:00:00 2001 From: Erik-Jan Westendorp Date: Mon, 4 Mar 2024 16:00:21 +0100 Subject: [PATCH 2/3] Change 'document type' to 'Document Type' --- 13/umbraco-cms/tutorials/custom-error-page.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/13/umbraco-cms/tutorials/custom-error-page.md b/13/umbraco-cms/tutorials/custom-error-page.md index 1f4c96fc938..c2df632824d 100644 --- a/13/umbraco-cms/tutorials/custom-error-page.md +++ b/13/umbraco-cms/tutorials/custom-error-page.md @@ -204,7 +204,7 @@ To **test this locally**, in Visual Studio replace `app.UseDeveloperExceptionPag #### Trigger a 500 error -You can trigger a 500 error on your frontend by changing a Model.Value property in your template. For example, on a document type with a property called `test`. The way to render it in the frontend would be `Model.Value("test");` To trigger a 500 error page you can add anything after Value such as `Model.ValueTest("test");` +You can trigger a 500 error on your frontend by changing a Model.Value property in your template. For example, on a Document Type with a property called `test`. The way to render it in the frontend would be `Model.Value("test");` To trigger a 500 error page you can add anything after Value such as `Model.ValueTest("test");` ## Maintenance Page From a79bc21a7532c627e4e0a7f6df9afe74796c0def Mon Sep 17 00:00:00 2001 From: Erik-Jan Westendorp Date: Mon, 4 Mar 2024 16:02:12 +0100 Subject: [PATCH 3/3] Update v12 --- 12/umbraco-cms/tutorials/custom-error-page.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/12/umbraco-cms/tutorials/custom-error-page.md b/12/umbraco-cms/tutorials/custom-error-page.md index 8067bd26924..16afa5a0ea6 100644 --- a/12/umbraco-cms/tutorials/custom-error-page.md +++ b/12/umbraco-cms/tutorials/custom-error-page.md @@ -206,7 +206,7 @@ To **test this locally**, in Visual Studio replace `app.UseDeveloperExceptionPag #### Trigger a 500 error -You can trigger a simple 500 error on your frontend by changing a Model.Value property in your template. For example, on a document type with a property called `test`. The way to render it in the frontend would be `Model.Value("test");` To trigger a 500 error page you can add anything after Value such as `Model.ValueTest("test");` +You can trigger a 500 error on your frontend by changing a Model.Value property in your template. For example, on a Document Type with a property called `test`. The way to render it in the frontend would be `Model.Value("test");` To trigger a 500 error page you can add anything after Value such as `Model.ValueTest("test");` ## Maintenance Page