You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -161,7 +161,7 @@ If you want to specify this yourself, add `IgnoredResourceExtensions` to the con
161
161
162
162
## Restricting access to the Admin UI
163
163
164
-
By default, only users of `Administrators` role can access Admin UI. But you can configure you authorization policy when registrating the NotFound handler.
164
+
By default, only users of `Administrators` role can access Admin UI. But you can configure your authorization policy when registering the NotFound handler.
165
165
166
166
```
167
167
services.AddNotFoundHandler(o => { },
@@ -171,15 +171,15 @@ By default, only users of `Administrators` role can access Admin UI. But you can
171
171
});
172
172
```
173
173
174
-
You can setup any policy rules you want.
174
+
You can set up any policy rules you want.
175
175
176
176
## Import
177
177
178
178
For details see [Import redirects for 404 handler](https://getadigital.com/blog/import-redirects-for-404-handler/) article.
179
179
180
180
# Custom 404 Page
181
181
182
-
To setup 404 page, you can use any method ASP.NET Core provides.
182
+
To set up 404 page, you can use any method ASP.NET Core provides.
183
183
184
184
One of the simplest solutions is adding a controller and a view for it that would display an error page:
185
185
@@ -275,7 +275,7 @@ It will monitor primary, secondary and SEO URLs:
275
275
Optimizely Content Cloud supports only primary URLs and Optimizely Commerce supports all three types of URLs.
276
276
277
277
There are two scheduled jobs:
278
-
-*[Geta NotFoundHandler] Index content URLs* - as mentioned before, this job indexes URLs of content. Usually, it is required to run this job only once. All new content is automatically indexed. But if for some reasons content publish events are not firing when creating new content (for example, during the import), then you should set this job to run frequently.
278
+
-*[Geta NotFoundHandler] Index content URLs* - as mentioned before, this job indexes URLs of content. Usually, it is required to run this job only once. All new content is automatically indexed. But if for some reason content publish events are not firing when creating new content (for example, during the import), then you should set this job to run frequently.
279
279
-*[Geta NotFoundHandler] Register content move redirects* - this job creates redirects based on registered moved content. Normally, this job is not required at all, but there might be situations when content move is registered but redirect creation is not completed. This could happen during deployments. In this case, you can manually run this job or schedule it to run time to time to fix such issues.
0 commit comments