#SCREENSTEPS CUSTOM ERROR PAGE CODE#

On this page, create the content that you want to display to users that request a service that is they do not have permissions for.

Create a page with title ForbiddenВ 403 and URL вЂ“ ~/forbidden-403.

In Error page URL name, enter forbidden-403.

Navigate to Administration В» Settings В» Advanced В» Pages В» Custom error pages В» Error types В» Create new.

Make sure custom error pages are enabled.

RECOMMENDATION: We recommend leaving Redirect checkbox deselected.Д®XAMPLE: If you want to configure a 403 custom error page that informs the user that the requested service is forbidden, perform the following: Otherwise, the error page is rendered on the URL that the user is currently trying to open.

Select Redirect checkbox, if you want the user to be redirected to the actual error pageвЂ™s URL.ДЇor example, ~/403-forbidden.

#SCREENSTEPS CUSTOM ERROR PAGE CODE#

If you do not want to use different error pages for the same error code or you do not want to translate your custom error page, enter the exact location of your page with tilde.ДЇor example, if your page is located on root level, under page Error pages, enter ~/error-pages/403 The URL name of the page, preceded by tilde.In this case, as URL name, you must enter /error-pages/403 and you must create the custom error page as a child of Error pages page. For example, you can have all of your error code pages under a group page Error pages with URL ~/error-pages.

This means that your error page is located under another page or group page. You can also enter a directory, followed by the exact URL of the error page. A directory, followed by the URL name of the page.You can also display different pages for the same error code, depending where the userвЂ™s request has produced the error.ДЇor more information about the behavior of the error pages, see Create the error pages and the provided example. This way, you can translate your page, if you use multiple languages. This allows you to use different error pages in different directories of your website. You enter the URL name in one of the following ways:ДЇor example, if the page URL is ~/403-forbidden, in Error page URL name, enter 403-forbidden.This is a normal Sitefinity CMS page that contains the information that you want to display when the error type is encountered. In Error page URL name, enter the exact URL of the page that you intend to use as custom error page.In HTTP status code, enter the code of the error type.ДЇor complete list of supported error codes, see Supported error codes.In the left tree, expand Pages В» Custom error pages and click Error types В» Create new.To complete the process, you need to create a Sitefinity CMS page with URL ~/404.

However, this does not mean that you automatically have working custom 404 page. NOTE: You have one preconfigured error type вЂ“ error type 404 page not found. The system displays the default ASP.NET error pages to all users вЂ“ the YSOD.

To disable custom error pages, select Disabled.

To localhost users, the system displays the default ASP.NET error pages вЂ“ the YSOD. The system displays the configured custom error pages to remote users. The system displays the configured custom error pages to all users вЂ“ remote and localhost.

To enable custom error pages, select one of the following:.

In the left tree, expand Pages and click Custom error pages.

In Sitefinity CMS backend, navigate to Administration В» Settings В» Advanced.

You configure error pages in the advanced Settings screen. For projects created with a version lower than 12.2 and then upgraded to version 12.2 or above, custom error pages are disabled. Additionally, error pages provide a much better way of informing the users that there is a problem with the resource they are trying to access.Д«y default, for projects created on Sitefinity CMS 12.2 or later, custom error pages are enabled. You must configure error pages to make sure such information is not visible on the live site. This is the default ASP.NET error screen that can contain sensitive information and make it visible to the public, for example your connection string or important variable names. This error screen is also known as YSOD or the вЂњyellow screen of deathвЂќ. In case your Sitefinity CMS website encounters a problem, your database server goes down, or your custom code throws an error, the user browsing the site is presented with an error screen. Custom error pages have a role for your website security and user browsing experience.

Screensteps custom error page