VERSION 10.0 is compiled for Sitecore 10.0 use and will not work on earlier versions.
Requires Sitecore 10.0
Requires .NET 4.8
Constellation is a collection of utilities for .NET CMS implementers.
The Foundation.Context namespace contains a contract for context-sensitive objects along with a context evaluator that compares
the sensitive instances' runtime settings against their configured scope.
The purpose of this library is to provide scoped pipeline handlers and rules to Sitecore to prevent developers from unintentionally executing
their customizations outside the scope of their current tenant|site|request.
Install-Package Constellation.Foundation.Contexts -Version 10.0.0.22019
dotnet add package Constellation.Foundation.Contexts --version 10.0.0.22019
<PackageReference Include="Constellation.Foundation.Contexts" Version="10.0.0.22019" />
paket add Constellation.Foundation.Contexts --version 10.0.0.22019
Updated Sitecore references to 10.0 minimum
- Sitecore.Kernel (>= 10.0.0)
NuGet packages (3)
Showing the top 3 NuGet packages that depend on Constellation.Foundation.Contexts:
Compatible with Sitecore 10.0 Requires Sitecore 10.0 Requires .NET Framework 4.8 Constellation is a collection of utilities for .NET CMS implementers. This small Feature contains a Sitecore Rule Action which must be installed in order to take advantage of this library. The package should self-install once you build and deploy your project. To use, an Item Saved rule must be created. The rule must have a condition that specifies that an Item is a "page" and therefore needs an SEO-friendly URL. The rule action should be the one included in this kit. Rule options include: - Replace Diacritics - Clear Display Name (recommended so that marketers see the actual Item name and therefore URL slug for pages) - Specify illegal characters to remove (Regex "\s" is a good choice.) - Replace spaces or remove spaces from names - Force lowercase It is up to the implementer to determine the nature of "page" Items. We recommend looking at Constellation.Foundation.Datasources for rule conditions that are suitable for this specific task. Note that the Illegal Characters option and the Replace Spaces option can conflict, a "-" will be removed if you use the "\W" regex, resulting in behavior similar to "Remove Spaces" We strongly recommend using "\s".
Compatible with Sitecore 10.0 Requires Sitecore 10.0 Requires .NET Framework 4.8 Constellation is a collection of utilities for .NET CMS implementers. The Feature.Redirects namespace contains two discrete functional components: Page Redirects: Items that are meant to be interspersed with Page type Items in the content tree so that dynamically generated navigation will list these Items as if they were part of that tree branch, although the actual target is elsewhere, or an entirely different site altogether. Marketing Redirects: Items that represent "short, catchy" URLs that then redirect deeper into the site. Also a way to teach search engines about URLs that have been permanently relocated. Marketing Redirects are managed through a discrete "application" in the Sitecore desktop. Exporting and importing redirect lists is supported. All redirects are tested for validity before they are allowed to be imported. The porting and development of this library has been kindly supported by Verndale (verndale.com)
Compatible with Sitecore 10.0 Requires Sitecore 10.0 Requires .NET Framework 4.8 Constellation is a collection of utilities for the Sitecore .NET CMS. The Foundation.PageNotFound library provides unique Sitecore-hosted "not found" pages with the correct 404 Http Response for each site in your installation. Installation 1. Add this NuGet package to your Sitecore solution 2. Build and Deploy your solution to a target environment Package Includes: Custom Site Attribute: notFoundPageID This attribute should be set to the ID of the Item to use for presenting 404 Response Status messages to the visitor. Each site requires its own 404 page Item. HttpRequestBegin Pipeline Processor: Page Not Found Resolver Assuming the site is configured with the ID of the "not found page" this processor will resolve the context item to that specific item if the context item is currently null. This processor must run after all Site, Database, Language, and Item resolvers, but before Device and Layout resolvers. The supplied patch:before is a safe bet, but may need to be changed depending on your solution. Please note that this processor will only run for databases and sites as configured, and should intentionally not run for Sitecore system sites. HttpRequestEnd Pipeline Processor: Set404StatusCode Assuming the site is configured with the ID of the "not found page" this processor will detect that the context item is the 404 page and will add the 404 code to the Response. Please note that the customizations in this processor will only run for databases and sites as configured, and should intentionally not run for Sitecore system sites.
This package is not used by any popular GitHub repositories.