This repository has been archived by the owner on May 30, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 14
Site Error Handling Overrides
David San Filippo edited this page Sep 11, 2017
·
1 revision
Category | Notes |
---|---|
Module Location | Foundation.Multisite |
Recommended | Yes |
Default | On |
Dependencies | None |
Pipelines Targeted | httpRequestBegin, replaces Sitecore: ExecuteRequest pipeline |
Events Targeted | None |
Site Settings | /sitecore/templates/SF/Foundation/Multisite/Interface Templates/_MultisitePageSettings |
Page Settings | None |
Patch Config | Foundation.Multisite\MultisitePageConfiguration.config |
Out of the box, Sitecore will redirect to pages for Item not found, layout not found, No Access and Login pages based on a global Site Setting. This is problematic in multi site solutions, so we have replaced this functionality with custom ones configurable at the site level through the use of custom Site Settings.
Note that Error Redirection is not supported by the Execute Pipeline, but instead leverages ASP.Net Error Handling. To get that feature to work properly, the ASP.Net Error should point to our custom Error Page, which uses the SiteConfiguration to redirect to the configured error page.
Introduction
- Getting Started
- Resources
- Supported Versions and Branches
- Sitecore Foundation for SxA
- Layer and Sitecore Dependencies
- Acknowledgements
Feature Guide
- Leveraging the Framework
- Site Configuration Management
- Information Architecture
- Dynamic Placeholders
- Handlebar Renderings
- Scripts and Styles
- Meta Tags
- Social Tags
- Redirect Manager
- Site Map
- IP White Listing
- PDF Generation
- Favicon
- Robots
- Parameterized Renderer
- Site and Feature Cache Cleaning
- Site Error Handling Overrides
- Shell Extensions
- Multilingual Features