df2b7dde3d
* Using Orchard.Mvc.FormValueRequiredAttribute instead of the FormValueRequiredAttribute class of the AdminController in the Orchard.Core.Contents namespace. * Removing obsoleted Spam value from the Orchard.Comments.Models.CommentStatus enum. * Removing the obsolete AddFilters method of the IFilterProvider interface in the Orchard.Mvc.Filters namespace. * Removing the obsolete LazyField<T> class from the Orchard.Core.Common.Utilities namespace. * Removing obsolete methods from OrchardLog4netLogger. * Removing obsolete Loader(Func<T, T> loader) method from LazyField.cs in the Orchard.ContentManagement.Utilities namespace. * Removing obsoleted ContentShapeResult ContentShape(IShape shape) method from ContentPartDriver. * Removing obsoleted ISessionLocator interface. * Removing obsoleted ContentFieldTemplate methods from ContentFieldDriver<TField>. * Removing obsoleted IMessagingChannel and IMessageManager interfaces, along with the migration step that updates the existing Send Email activities to use the new Message Queueing functionality. * Removing obsoleted CustomStepsStep. Don't need the CustomStepsStep RecipeBuilderStep because you can implement IRecipeBuilderStep and IRecipeExecutionStep instead of implementing custom export steps. * Removing obsoleted CustomPropertiesPart. It used to be necessary for the List feature (also obsolete) to be able to sort on custom data. * Removing the obsoleted ITaskLeaseService with its default implementation. Removing deprecated Orchard.TaskLease module because it only contains this interface with its default implementation. Use Orchard.Tasks.Locking.IDistributedLockService instead. * Removing LegacyRulesEvaluator. This condition provider was there for backwards compatibility during the deprecation period. * Removing IRuleManager with its default implementation. Use Orchard.Conditions.Services.ConditionManager instead. * Removing unused RequiresOwnership permission. * Reverting unnecessary sln file changes * Resolving IMessageChannelSelector instead of IMessageManager in editor templates * Removing commented out code from ContentPartDriverCoordinatorTests * Removing Orchard.jQuery too since its quite outdated and Orchard.Resources has been available since 1.9 * Readding the migration step that updates the existing Send Email activities --------- Co-authored-by: Benedek Farkas <benedek.farkas@lombiq.com>
Orchard
Orchard is a free, open source, community-focused Content Management System built on the ASP.NET MVC platform. You are looking at Orchard 1, the older, .NET Framework-based version that has been in development since 2009.
If you're starting a new project (or maintaining a project built on Orchard 1), you should check out Orchard Core, the new generation of Orchard built on ASP.NET Core. You can also try it for free on DotNest.com!
Join the community discussion on Discord, where we also have a channel dedicated to Orchard 1.
About The Orchard Project
Please visit our website at https://orchardcore.net for the most current information about this project.
Orchard is a free, open source, community-focused Content Management System built on the ASP.NET MVC platform.
Orchard is built on a modern architecture that puts extensibility up-front, as its number one concern. All components in Orchard can be replaced or extended. Content is built from easily composable building blocks. Modules extend the system in a very decoupled fashion, where a commenting module for example can as easily apply to pages, blog posts, photos or products. A rich UI composition system completes the picture and ensures that you can get the exact presentation that you need for your content.
Orchard is delivered under the .NET Foundation. It is licensed under a New BSD license, which is approved by the OSI.
Our mission is to empower our users and foster a dedicated and diverse community that builds the CMS that we all want to use.
Project Status
Orchard is currently in version 1.10.4: It contains bugfixes and the more impactful changes and new features added in the latest major version (1.10).
We invite participation by the developer community in shaping the project's direction, so that we can publicly validate our designs and development approach. All our releases are available on our Releases page, and we encourage interested developers to check out the source code on the Orchard GitHub site and get involved with the project.
How To Get Involved
We hope that by engaging with the community we will continue to shape Orchard into a valuable set of tools and applications. The Orchard team is committed to open community participation and accepts code contributions. We encourage community participation at all levels from general project feedback to bug fixes and patches.
There are many ways you can contribute to Orchard: