bc74aec232
The content field harvester throws an error when the LayoutEditor is rendered without having a content item as the context (BluePrints, for example). The previous code would fall back to simply enumerating all fields of all parts to make available all content fields as elements. However, the content field elements can't render these fields without having a proper content item as context, so it would fail with an exception. There are scenarios where one might still want to be able to add content field elements on the canvas even when there is no current content item (to create template layouts for example). But to support this, we need to figure out what we want to render if we can;t actually render the content field at design time. Perhaps a simplified representation would suffice in this scenario. To be discussed. Removing the broken feature for now.
Orchard
Orchard is a free, open source, community-focused Content Management System built on the ASP.NET MVC platform.
You can try it for free on DotNest.com or on Microsoft Azure by clicking on this button.
About The Orchard Project
Please visit our website at http://orchardproject.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.1: 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 it's easy to Install Orchard using the Web Platform Installer as well. 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:
- Check out the code
- Write documentation
- Find and file a bug
- Propose a feature idea
- Ask and answer questions in our forums and on Stack Overflow
- Participate in our gitter.im chatroom
- Participate in forum discussions
- Submit a pull request
- Translate Orchard
- Contribute modules and themes to our gallery
- Send us feedback
The Future Of Orchard CMS: Orchard 2
As the underlying frameworks (.NET, ASP.NET and ASP.NET MVC) are constantly evolving, Orchard of course keeps track of the changes and improvements of these: Orchard 2 is the next generation of Orchard releases that is based on ASP.NET Core. Just like the current Orchard project, it's fully open-source and is publicly available on GitHub. Orchard 2 (as a framework) is being built from scratch: it's still in development and does not share any of its code base (at least directly) with the current versions of Orchard.