Version 3.0.0-alpha007

New alpha release for Umbraco 9. This release will not work on older versions of Umbraco.

#installation">Installation

Via NuGet:

.NET CLI:

dotnet add package Skybrud.Umbraco.Redirects --version 3.0.0-alpha007

Package Manager:

Install-Package Skybrud.Umbraco.Redirects -Version 3.0.0-alpha007

#changelog">Changelog

• Updated redirects middleware to set correct status code (see #117 and 2b16495)
  In previous release for Umbraco 9, the middleware would always set a 302 Found status regardless of the type of the redirect saved in the database. With this commit, the status will either be 301 Moved Permanently or 307 Temporary Redirect depending on the type of the saved redirect.

• Updated how the package is configured during installation (see #115 and c699a4a)
  If the redirects package was installed before the upgrade installer was finished, two exceptions would occur:

  • Migration to install the database would fail as the database isn't during before the Umbraco installer has been completed.
  • Middleware would also run when trying to access the Umbraco installer, thus failing as the middleware would try to access the database through the redirects service

  With this commit, the migration plan for the redirects package will only be set up when the runtime level is Run.

  The middleware will now not run when the runtime level is Install, but will still run when the runtime level is Upgrade. This might need a bit more testing, but seems to be fine as there is a database at this level.

• Introducing interfaces for the Redirect and RedirectDestination classes (see 3e311d1)
  The new interfaces are named IRedirect and IRedirectDestination respectively.

• Fixed incorrect destination warning (see ce6f420)
  The redirects dashboard shows a warning if the destination is content or media, and the destination is either unpublished, trashed or deleted.

  The dashboard would incorrectly show an unpublished warning for redirects have been deleted. With this commit, the correct warning is now being returned by the underlying API, so the dashboard doesn't have to check other properties to determine whether a warning should be shown, and if so, what it should show.

• Added support for searching redirects by their ID or key (see 5461bf6)
  The dashboard has never been good for looking up redirects by either their IDs or GUID keys. With this commit, both is now possible.

• Fixed incorrect media anchor link in the redirects dashboard (see c95b916)
  The dashboard still used the variable name from the V8 package, which is different.