91a82535a2
* Added tokenizable default value to ContentPickerFields (#8351) * Fixes errors during Indexing (#8349) * Added admin search permissions (#8346) * Reuse Settings_ShellDescriptorRecord during an http request (#8355) * Added a new index to CommonPartRecord (#8362) * Attempted AutoroutePart improvement (#8360) This should ease Database issues, because it short circuits some code paths through aliases. * Save MemberBindingRecords in memory (#8371) Prevent fetching the same table from the database 5+ times per request by loading it and saving it in a private property for a request. * Cache list of configured layers (#8373) On every page load on frontend we were querying for all existing layers to test for the ones that are currently active. Since that information is not bound to change often, we added a cache layer to prevent querying every time. The cache is evicted whenever a Layer gets updated. * Memorize query results in blog service (#8374) The query for all published blogs is being called twice while building the admin menu, so we are memorizing its results. * Updated UI for projections (#8380) Some textboxes were too small for the actual text users would generally write in them. Those meant to hold HTML have been converted to textareas. * Process ignored paths while being aware of RequestUrlPrefix (#8384) * Process ignored paths while being aware of RequestUrlPrefix * Fix: I had moved a Trim to the wrong place * Fixed issue with empty/uninitialized null set of ignored urls * tokens sort criteria (#8382) * Tokenized state for sort criteria * Tokenized state also in the other place where sort criteria are used * Remove lock from the dictionary when the task has completed. (#8395) Fixes #8391 * Update DistributedLockService.cs (#8398) * fix for CPF when other scripts are also adding to sessionStorage (#8404) * Fixes Boolean Conversion error (#8393) * Fix/8392 remeber me model state exception (#8410) @sebastienros this fixes the possible NRE that would happen for absent models from merged #8393 (see your comment there https://github.com/OrchardCMS/Orchard/pull/8393#issuecomment-686630198) * Removed changes to model bindings (#8412) This is the same as reverting 1.10.x to commit |
||
|---|---|---|
| lib | ||
| src | ||
| .deployment | ||
| .gitattributes | ||
| .gitignore | ||
| .hgeol | ||
| build.cmd | ||
| CalculateBindingRedirects.ps1 | ||
| CleanSolution.ps1 | ||
| ClickToBuild.cmd | ||
| CREDITS.txt | ||
| DeleteModuleBinaries.cmd | ||
| deploy.cmd | ||
| deploy.ps1 | ||
| DeploymentUtility.psm1 | ||
| LICENSE.txt | ||
| Orchard.proj | ||
| README.md | ||
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 https://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.3: 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:
- Check out the code
- Write documentation
- Find and file a bug
- Propose a feature idea
- Ask and answer questions on Stack Overflow
- Participate in our gitter.im chatroom
- Submit a pull request
- Translate Orchard
- Contribute modules and themes to our gallery
The Future Of Orchard CMS: Orchard Core
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 Core 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 Core (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 (1.x) of Orchard.