Inbound link errors is a simple Umbraco Back-Office package that tracks 404 responses so that you can add a redirect to them. It includes a dashboard in Umbraco where the user is able to add it as a new redirect, delete it or hide it. Utilizes ngTable for an AngularJs driven data table which includes ordering by column, simple pagination and searching. Links are only tracked at the end of the pipeline and if the request resulted in a 404 response.
The dashboard for the inbound link errors has multiple filters that can be used:
Download the nuget package: Install-Package InboundLinkErrors or install it through Umbraco packages. After installing, make sure the following two lines can be found in your Web.config. Without it, the application will not be able to track your 404 responses.
<configuration> ... <system.webServer> ... <modules> ... <remove name="LinkErrorsHttpModule"/> <add name="LinkErrorsHttpModule" type="InboundLinkErrors.Core.LinkErrorsHttpModule, InboundLinkErrors" /> </modules> </system.webServer> </configuration>
There are various configuration that you can setup in your web config app settings. Simply add the following to your appsettings to change any of the configuration values:
<configuration> ... <appSettings> ... <add key="[Config Key]" value="[Config Value]" /> </appSettings></configuration>
The configuration options are as follows:
By default, the plugin will write your new redirects to the Url tracker of Umbraco. You are however able to change this to with any of the following packages:
If you want to connect the InboundLinkErrors to the SimpleRedirects plugin, you can download the following nuget package: Install InboundLinkErrors.SimpleRedirects. This will connect the InboundLinkErrors package to the SimpleRedirects package.
Currently work in progress!
InboundLinkErrors is located at the content section as one of the dashboards. When clicking on the dashboard called "Link errors", you'll be taken to the dashboard of InboundLinkErrors.
Once arrived, you'll usually see nothing in the table yet. This is probably because no requests with a 404 response have been made yet. When a 404 response is given, InboundLinkErrors will track it in the dashboard. You also have the option to filter on Hidden and Media requests.
When a 404 response is tracked, you'll be able to perform 3 actions on it:
Support: Issues/feature tracker