Skip to content

Commit 5326e3f

Browse files
committed
Some formatting fixes
1 parent e7ab009 commit 5326e3f

File tree

3 files changed

+27
-30
lines changed

3 files changed

+27
-30
lines changed

14/umbraco-cms/tutorials/custom-error-page.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -30,13 +30,11 @@ This has been moved to a separate article: [Create a custom maintenance page](cr
3030

3131
A 404 error occurs when a requested page cannot be found—typically because the content has been deleted, the URL path has changed, or the visitor typed an invalid path. In Umbraco, you can create and configure custom 404 pages using content from the backoffice.
3232

33-
This section shows how to set up a custom 404 page:
34-
3533
### Create a 404 page in the backoffice
3634

3735
1. Go to the **Settings** section in the Umbraco backoffice.
3836
2. Create a new **Document Type with Template**.
39-
3. Name the Document Type **ErrorPage404**.
37+
3. Name the Document Type *ErrorPage404*.
4038
4. [Optional] Add any custom properties you want — though most 404 pages are static.
4139
5. Click **Save**.
4240
6. Go to the **Templates** folder.
@@ -49,7 +47,7 @@ This section shows how to set up a custom 404 page:
4947
2. Name it **Statuscodes**.
5048
3. Go to the **Structure** Workspace view.
5149
* Enable **Allow at root**.
52-
* Add the **ErrorPage404** Document Type as an **Allowed child node types**.
50+
* Add the *ErrorPage404* Document Type as an **Allowed child node types**.
5351
* Click **Choose**.
5452
4. Click **Save**.
5553

@@ -58,9 +56,10 @@ This section shows how to set up a custom 404 page:
5856
1. Go to the **Content** section.
5957
2. Create a new content node based on the **Statuscodes** Document Type and name it **Statuscodes**.
6058
3. Click **Save** or **Save and Publish**.
61-
4. Under it, create a child node using the **ErrorPage404** Document Type.
59+
4. Under it, create a child node using the *ErrorPage404* Document Type.
6260
5. Name it *Page 404 Not Found* or similar.
6361
* This will be the content shown when a 404 error occurs.
62+
6. Click **Save** or **Save and Publish**.
6463

6564
### Configure the Error Page in `appsettings.json` file
6665

@@ -111,11 +110,11 @@ Each entry maps a culture to its specific 404 page using the content’s GUID.
111110

112111
### Set a custom 404 page using IContentLastChanceFinder
113112

114-
It is also possible to set up a 404 error page programmatically using `IContentLastChanceFinder`. To learn more about `IContentLastChanceFinder` read the [Custom Routing](../implementation/custom-routing/)article.
113+
It is also possible to set up a 404 error page programmatically using `IContentLastChanceFinder`. To learn more about `IContentLastChanceFinder`, read the [Custom Routing](../implementation/custom-routing/) article.
115114

116-
Before following this example, follow the [Create a 404 page in the backoffice](custom-error-page.md#create-a-404-page-in-the-backoffice) part. The example below will use the `errorPage404` alias of the Document Type to find and display the error page.
115+
Before following this example, follow the [Create a 404 page in the backoffice](custom-error-page.md#create-a-404-page-in-the-backoffice) part. The example below will use the *errorPage404* alias of the Document Type to find and display the error page.
117116

118-
1. Create a new `.cs` file called `Error404Page` at the root of the project.
117+
1. Create a new `.cs` file called *Error404Page* at the root of the project.
119118
2. Add the following code to the newly created class:
120119

121120
{% code title="Error404Page.cs" lineNumbers="true" %}
@@ -195,7 +194,7 @@ This section guides you in setting up a custom page for handling internal server
195194
2. Name it **Statuscodes**.
196195
3. Go to the **Structure** Workspace view.
197196
* Enable **Allow at root**.
198-
* Add the **ErrorPage500** Document Type as an **Allowed child node types**.
197+
* Add the *ErrorPage500* Document Type as an **Allowed child node types**.
199198
* Click **Choose**.
200199
4. Click **Save**.
201200

@@ -204,7 +203,7 @@ This section guides you in setting up a custom page for handling internal server
204203
1. Go to the **Content** section.
205204
2. Create a new content node based on the **Statuscodes** Document Type and name it **Statuscodes**.
206205
3. Click **Save** or **Save and Publish**.
207-
4. Under it, create a child node using the **ErrorPage500** Document Type.
206+
4. Under it, create a child node using the *ErrorPage500* Document Type.
208207
5. Name it *Page 500* or similar.
209208
* This will be the content shown when a 500 error occurs.
210209

15/umbraco-cms/tutorials/custom-error-page.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -30,13 +30,11 @@ This has been moved to a separate article: [Create a custom maintenance page](cr
3030

3131
A 404 error occurs when a requested page cannot be found—typically because the content has been deleted, the URL path has changed, or the visitor typed an invalid path. In Umbraco, you can create and configure custom 404 pages using content from the backoffice.
3232

33-
This section shows how to set up a custom 404 page:
34-
3533
### Create a 404 page in the backoffice
3634

3735
1. Go to the **Settings** section in the Umbraco backoffice.
3836
2. Create a new **Document Type with Template**.
39-
3. Name the Document Type **ErrorPage404**.
37+
3. Name the Document Type *ErrorPage404*.
4038
4. [Optional] Add any custom properties you want — though most 404 pages are static.
4139
5. Click **Save**.
4240
6. Go to the **Templates** folder.
@@ -49,7 +47,7 @@ This section shows how to set up a custom 404 page:
4947
2. Name it **Statuscodes**.
5048
3. Go to the **Structure** Workspace view.
5149
* Enable **Allow at root**.
52-
* Add the **ErrorPage404** Document Type as an **Allowed child node types**.
50+
* Add the *ErrorPage404* Document Type as an **Allowed child node types**.
5351
* Click **Choose**.
5452
4. Click **Save**.
5553

@@ -58,9 +56,10 @@ This section shows how to set up a custom 404 page:
5856
1. Go to the **Content** section.
5957
2. Create a new content node based on the **Statuscodes** Document Type and name it **Statuscodes**.
6058
3. Click **Save** or **Save and Publish**.
61-
4. Under it, create a child node using the **ErrorPage404** Document Type.
59+
4. Under it, create a child node using the *ErrorPage404* Document Type.
6260
5. Name it *Page 404 Not Found* or similar.
6361
* This will be the content shown when a 404 error occurs.
62+
6. Click **Save** or **Save and Publish**.
6463

6564
### Configure the Error Page in `appsettings.json` file
6665

@@ -111,11 +110,11 @@ Each entry maps a culture to its specific 404 page using the content’s GUID.
111110

112111
### Set a custom 404 page using IContentLastChanceFinder
113112

114-
It is also possible to set up a 404 error page programmatically using `IContentLastChanceFinder`. To learn more about `IContentLastChanceFinder` read the [Custom Routing](../implementation/custom-routing/)article.
113+
It is also possible to set up a 404 error page programmatically using `IContentLastChanceFinder`. To learn more about `IContentLastChanceFinder`, read the [Custom Routing](../implementation/custom-routing/) article.
115114

116-
Before following this example, follow the [Create a 404 page in the backoffice](custom-error-page.md#create-a-404-page-in-the-backoffice) part. The example below will use the `errorPage404` alias of the Document Type to find and display the error page.
115+
Before following this example, follow the [Create a 404 page in the backoffice](custom-error-page.md#create-a-404-page-in-the-backoffice) part. The example below will use the *errorPage404* alias of the Document Type to find and display the error page.
117116

118-
1. Create a new `.cs` file called `Error404Page` at the root of the project.
117+
1. Create a new `.cs` file called *Error404Page* at the root of the project.
119118
2. Add the following code to the newly created class:
120119

121120
{% code title="Error404Page.cs" lineNumbers="true" %}
@@ -195,7 +194,7 @@ This section guides you in setting up a custom page for handling internal server
195194
2. Name it **Statuscodes**.
196195
3. Go to the **Structure** Workspace view.
197196
* Enable **Allow at root**.
198-
* Add the **ErrorPage500** Document Type as an **Allowed child node types**.
197+
* Add the *ErrorPage500* Document Type as an **Allowed child node types**.
199198
* Click **Choose**.
200199
4. Click **Save**.
201200

@@ -204,7 +203,7 @@ This section guides you in setting up a custom page for handling internal server
204203
1. Go to the **Content** section.
205204
2. Create a new content node based on the **Statuscodes** Document Type and name it **Statuscodes**.
206205
3. Click **Save** or **Save and Publish**.
207-
4. Under it, create a child node using the **ErrorPage500** Document Type.
206+
4. Under it, create a child node using the *ErrorPage500* Document Type.
208207
5. Name it *Page 500* or similar.
209208
* This will be the content shown when a 500 error occurs.
210209

16/umbraco-cms/tutorials/custom-error-page.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -30,13 +30,11 @@ This has been moved to a separate article: [Create a custom maintenance page](cr
3030

3131
A 404 error occurs when a requested page cannot be found—typically because the content has been deleted, the URL path has changed, or the visitor typed an invalid path. In Umbraco, you can create and configure custom 404 pages using content from the backoffice.
3232

33-
This section shows how to set up a custom 404 page:
34-
3533
### Create a 404 page in the backoffice
3634

3735
1. Go to the **Settings** section in the Umbraco backoffice.
3836
2. Create a new **Document Type with Template**.
39-
3. Name the Document Type **ErrorPage404**.
37+
3. Name the Document Type *ErrorPage404*.
4038
4. [Optional] Add any custom properties you want — though most 404 pages are static.
4139
5. Click **Save**.
4240
6. Go to the **Templates** folder.
@@ -49,7 +47,7 @@ This section shows how to set up a custom 404 page:
4947
2. Name it **Statuscodes**.
5048
3. Go to the **Structure** Workspace view.
5149
* Enable **Allow at root**.
52-
* Add the **ErrorPage404** Document Type as an **Allowed child node types**.
50+
* Add the *ErrorPage404* Document Type as an **Allowed child node types**.
5351
* Click **Choose**.
5452
4. Click **Save**.
5553

@@ -58,9 +56,10 @@ This section shows how to set up a custom 404 page:
5856
1. Go to the **Content** section.
5957
2. Create a new content node based on the **Statuscodes** Document Type and name it **Statuscodes**.
6058
3. Click **Save** or **Save and Publish**.
61-
4. Under it, create a child node using the **ErrorPage404** Document Type.
59+
4. Under it, create a child node using the *ErrorPage404* Document Type.
6260
5. Name it *Page 404 Not Found* or similar.
6361
* This will be the content shown when a 404 error occurs.
62+
6. Click **Save** or **Save and Publish**.
6463

6564
### Configure the Error Page in `appsettings.json` file
6665

@@ -111,11 +110,11 @@ Each entry maps a culture to its specific 404 page using the content’s GUID.
111110

112111
### Set a custom 404 page using IContentLastChanceFinder
113112

114-
It is also possible to set up a 404 error page programmatically using `IContentLastChanceFinder`. To learn more about `IContentLastChanceFinder` read the [Custom Routing](../implementation/custom-routing/)article.
113+
It is also possible to set up a 404 error page programmatically using `IContentLastChanceFinder`. To learn more about `IContentLastChanceFinder`, read the [Custom Routing](../implementation/custom-routing/) article.
115114

116-
Before following this example, follow the [Create a 404 page in the backoffice](custom-error-page.md#create-a-404-page-in-the-backoffice) part. The example below will use the `errorPage404` alias of the Document Type to find and display the error page.
115+
Before following this example, follow the [Create a 404 page in the backoffice](custom-error-page.md#create-a-404-page-in-the-backoffice) part. The example below will use the *errorPage404* alias of the Document Type to find and display the error page.
117116

118-
1. Create a new `.cs` file called `Error404Page` at the root of the project.
117+
1. Create a new `.cs` file called *Error404Page* at the root of the project.
119118
2. Add the following code to the newly created class:
120119

121120
{% code title="Error404Page.cs" lineNumbers="true" %}
@@ -195,7 +194,7 @@ This section guides you in setting up a custom page for handling internal server
195194
2. Name it **Statuscodes**.
196195
3. Go to the **Structure** Workspace view.
197196
* Enable **Allow at root**.
198-
* Add the **ErrorPage500** Document Type as an **Allowed child node types**.
197+
* Add the *ErrorPage500* Document Type as an **Allowed child node types**.
199198
* Click **Choose**.
200199
4. Click **Save**.
201200

@@ -204,7 +203,7 @@ This section guides you in setting up a custom page for handling internal server
204203
1. Go to the **Content** section.
205204
2. Create a new content node based on the **Statuscodes** Document Type and name it **Statuscodes**.
206205
3. Click **Save** or **Save and Publish**.
207-
4. Under it, create a child node using the **ErrorPage500** Document Type.
206+
4. Under it, create a child node using the *ErrorPage500* Document Type.
208207
5. Name it *Page 500* or similar.
209208
* This will be the content shown when a 500 error occurs.
210209

0 commit comments

Comments
 (0)