Skip to content

Orchard 1.10

建立：1.10

Published: 3/18/2016

发布时间：2016年3月18日

How to Install Orchard

如何安装Orchard

To install Orchard using Web PI, follow these instructions:

要使用Web PI安装Orchard，请按照以下说明操作：

http://docs.orchardproject.net/Documentation/Installing-Orchard.

http://docs.orchardproject.net/Documentation/Installing-Orchard。

Web PI will detect your hardware environment and install the application.

Web PI将检测您的硬件环境并安装该应用程序。

Alternatively, to install the release manually, download the Orchard.Web.1.10.zip file.

或者，要手动安装发行版，请下载Orchard.Web.1.10.zip文件。

http://docs.orchardproject.net/Documentation/Manually-installing-Orchard-zip-file

http://docs.orchardproject.net/Documentation/Manually-installing-Orchard-zip-file

The zip contents are pre-built and ready-to-run. Simply extract the contents of the Orchard

zip内容是预先构建的并且可以立即运行。只需提取果园的内容即可

folder from the zip contents to an IIS virtual directory (or site root) and then point your

从zip内容到IIS虚拟目录（或站点根目录）的文件夹，然后指向您的

browser to the site. You can also just extract to a local folder and open the Orchard

浏览器到网站。您也可以只提取到本地文件夹并打开Orchard

folder in Visual Studio or WebMatrix as a web site (but not as a web application).

Visual Studio或WebMatrix中的文件夹作为Web站点（但不是Web应用程序）。

Please make sure you have a machine key

请确保您有机器钥匙

http://docs.orchardproject.net/Documentation/Setting-up-a-machine-key

http://docs.orchardproject.net/Documentation/Setting-up-a-machine-key

or you may experience frequent disconnections.

或者您可能会经常断开连接。

What file to download?

要下载什么文件？

If you just want to use Orchard and don't care about the source code, Orchard.Web.zip

如果你只是想使用Orchard而不关心源代码，Orchard.Web.zip

is what you want to use, preferably through the WebPI instructions.

是你想要使用的，最好是通过WebPI指令。

Do not attempt to build the WebPI version in VS. Use the full source if you want to use VS.

不要尝试在VS中构建WebPI版本。如果要使用VS，请使用完整源代码。

If you want to take a look at the source code or want to be able to build the application in Visual Studio,

如果您想查看源代码或希望能够在Visual Studio中构建应用程序，

Orchard.Sources.1.10.zip is fine.

Orchard.Sources.1.10.zip很好。

If you want to setup a development environment for patch or module development,

如果要为修补程序或模块开发设置开发环境，

you should clone the repository by following the instructions here:

您应该按照此处的说明克隆存储库：

http://docs.orchardproject.net/Documentation/Setting-up-a-source-enlistment

http://docs.orchardproject.net/Documentation/Setting-up-a-source-enlistment

Branches are described here: http://docs.orchardproject.net/Documentation/Developer-FAQ#Whatarethedefaultanddevbranches?WhichoneshouldIbeusing?

分支在这里描述：http://docs.orchardproject.net/Documentation/Developer-FAQ#Whatarethedefaultanddevbranches?WhichoneshouldIbeusing？

Who should use this software?

谁应该使用这个软件？

This software is in version 1.10. The code is in a stable state and constitutes

该软件的版本为1.10。代码处于稳定状态并构成

a solid foundation for building applications, themes and modules.

为构建应用程序，主题和模块奠定坚实的基础。

Suggestions are welcome in the discussion forums.

欢迎在论坛中提出建议。

You are allowed to use this software in any way that is compatible with the new BSD license.

您可以以与新BSD许可证兼容的任何方式使用此软件。

This includes commercial derivative work.

这包括商业衍生作品。

What's new?

什么是新的？

Orchard 1.10 includes all the changes from version 1.9.3 http://docs.orchardproject.net/Documentation/Orchard-1-9-3.Release-Notes and introduces the following changes and features:

Orchard 1.10包含版本1.9.3 http://docs.orchardproject.net/Documentation/Orchard-1-9-3.Release-Notes中的所有更改，并介绍了以下更改和功能：

Features

特征

  • Default values for content fields

  • 内容字段的默认值 *

  • Configurable locations for Modules and Themes (see this documentation page on how to configure them)

  • 模块和主题的可配置位置（[请参阅此文档页面，了解如何配置它们]（http://docs.orchardproject.net/en/latest/Documentation/Orchard-module-loader-and-dynamic-compilation/#custom-文件夹）） *

  • Parameterized snippets

  • 参数化片段 *

  • Orchard.Resources now contains common assets to be reused across core modules

  • Orchard.Resources现在包含可在核心模块之间重用的公共资产 *

  • Layer rules have been moved to Orchard.Conditions for reusability

  • 层规则已移至Orchard.Conditions以获得可重用性 *

  • Orchard.TaskLease has been deprecated in favor of distributed locks

  • Orchard.TaskLease已被弃用，转而支持分布式锁 *

  • Orchard.jQuery has been deprecated in favor of Orchard.Resources

  • Orchard.jQuery已被弃用，转而使用Orchard.Resources *

  • Editor tabs support

  • 编辑器标签支持 *

Improvements

改进

  • Use of Nuget packages instead of the /lib folder

  • 使用Nuget包而不是/ lib文件夹 *

  • New extension methods for migrations

  • 迁移的新扩展方法 *

  • Upgraded to .NET 4.5.2

  • 升级到.NET 4.5.2 *

  • Recipes and Import/Export improvements

  • 食谱和进口/出口改进 *

  • Orchard.exe help command enhancement

  • Orchard.exe帮助命令增强 *

Bugs

错误

Bug fixes are listed in the 1.9.3 release notes.

错误修复在[1.9.3发行说明]中列出（http://docs.orchardproject.net/Documentation/Orchard-1-9-3.Release-Notes）。

The full list of fixed bugs for this release can be found here:

可以在此处找到此版本的已修复错误的完整列表：

  • Bugs fixed in 1.10.

  • [错误修复于1.10]（https://github.com/OrchardCMS/Orchard/issues?q=is%3Aissue+milestone%3A%22Orchard+1.10%22+is%3Aclosed）。 *

How to upgrade from a previous version

如何从以前的版本升级

You can find migration instructions here: http://docs.orchardproject.net/Documentation/Upgrading-a-site-to-a-new-version-of-Orchard.

您可以在此处找到迁移说明：http://docs.orchardproject.net/Documentation/Upgrading-a-site-to-a-new-version-of-Orchard。

No matter what migration path you take, please take the precaution of making a backup of your site and database first.

无论您采用何种迁移路径，请首先预防备份您的站点和数据库。

Upgrading from Orchard 1.9 and earlier

从Orchard 1.9及更早版本升级

Please follow the upgrade instruction from this document: http://docs.orchardproject.net/en/latest/Documentation/Orchard-1-9.Release-Notes/

请按照本文档中的升级说明进行操作：http://docs.orchardproject.net/en/latest/Documentation/Orchard-1-9.Release-Notes/

Disabled modules

已禁用的模块

Some modules are not loaded automatically and need to be enabled manually if you are using them:

某些模块未自动加载，如果您使用它们需要手动启用：

  • Orchard.Workflows.Timer

  • Orchard.Workflows.Timer

  • Orchard.Email.Workflow

  • Orchard.Email.Workflow

  • Orchard.Users.Workflows

  • Orchard.Users.Workflows

  • Orchard.Roles.Workflows

  • Orchard.Roles.Workflows

Themes & Layouts

主题和布局

If you are using the Orchard.Layouts module you might need to integrate a custom css file to support the grid system.

如果您使用的是Orchard.Layouts模块，则可能需要集成自定义css文件以支持网格系统。

Layouts is using some default classes like span-4, which was added automatically by the module but could conflict with the ones in other grid frameworks.

Layouts正在使用一些默认类，如span-4，它是由模块自动添加的，但可能与其他网格框架中的类冲突。

It's no more added by default. TheThemeMachine is importing it by itself. Most Bootstrap theme should already override the Layout's tagging to incorporate its custom classes.

默认情况下不再添加它。 TheTheMachine自己导入它。大多数Bootstrap主题应该已经覆盖Layout的标记以合并其自定义类。

If this file is necessary for your theme you will need to add it back to it:

如果您的主题需要此文件，则需要将其添加回主题：

https://github.com/OrchardCMS/Orchard/blob/dev/src/Orchard.Web/Modules/Orchard.Layouts/Styles/default-grid.css

Deprecated modules

不推荐使用的模块

If your modules were using files or resources from Orchard.jQuery you will need to point to the ones defined in Orchard.Resources.

如果您的模块使用Orchard.jQuery中的文件或资源，则需要指向Orchard.Resources中定义的文件或资源。

If your modules were using services from Orchard.TaskLease you will need to use IDistributedLock instead.

如果您的模块使用的是Orchard.TaskLease中的服务，则需要使用IDistributedLock。

JetBrains annotations has been removed

JetBrains注释已被删除

If your modules were using some of these attributes you will need to remove them or to include them back into your projects.

如果您的模块使用其中一些属性，则需要删除它们或[包含它们]（https://github.com/OrchardCMS/Orchard/blob/1.9.3/src/Orchard/Validation/JetBrains.Annotations。 cs）回到你的项目。

Nuget packages

Nuget包

Because we have moved to using Nuget packages instead of the /lib folder, you will need to point to the same Nuget packages if you were using the /lib folder.

因为我们已经开始使用Nuget包而不是/ lib文件夹，所以如果使用/ lib文件夹，则需要指向相同的Nuget包。

@qt1 has created a script to help with the migration to Nuget here: https://github.com/OrchardCMS/Orchard/issues/6529

@ qt1创建了一个脚本来帮助迁移到Nuget：https：//github.com/OrchardCMS/Orchard/issues/6529

Database constraints

数据库约束

Orchard 1.10 contains new database contraints to prevent corrupted data. One of them might fail if you already have duplicated content item versions.

Orchard 1.10包含新的数据库约束以防止数据损坏。如果您已经有重复的内容项版本，其中一个可能会失败。

To check if you have some you can run this query and delete the duplicated entries.

要检查是否有一些，您可以运行此查询并删除重复的条目。 


SELECT [Number], [ContentItemRecord_id], COUNT(*) 

 <font color=#0099ff size=4 face="黑体">SELECT [Number]，[ContentItemRecord_id]，COUNT（*）</font> 


FROM [Orchard_Framework_ContentItemVersionRecord]

 <font color=#0099ff size=4 face="黑体">FROM [Orchard_Framework_ContentItemVersionRecord]</font> 


GROUP BY [Number], [ContentItemRecord_id]

 <font color=#0099ff size=4 face="黑体">GROUP BY [Number]，[ContentItemRecord_id]</font> 


HAVING ( COUNT(*) > 1 )

 <font color=#0099ff size=4 face="黑体">HAVING（COUNT（*）> 1）</font>

Warning on Workflows localization fixes

关于工作流本地化修复的警告

Due to a fix on how Workflows activity outcomes (e.g. "Done") are localized, after upgrading to Orchard 1.10 part of the connections between Workflows activities will get lost on a site that uses a localized (non-English) admin area and you'll have to re-connect activities. How many connections get lost depends on the completeness of the localization package for the Workflows module.

由于修复了工作流活动结果（例如“完成”）的本地化，在升级到Orchard 1.10之后，工作流活动之间的部分连接将在使用本地化（非英语）管理区域的站点上丢失，并且您'我必须重新连接活动。丢失的连接数取决于Workflows模块的本地化包的完整性。

Thus make sure to take notes of the structure of your workflows before upgrading if your site's admin area is using a culture other than an English one and has a localization package installed. If your site doesn't make use of Workflows, uses and English-speaking culture or doesn't have a localization package installed then it's not affected.

因此，如果您的站点的管理区域使用的是非英语文化并且安装了本地化软件包，请务必在升级之前记录您的工作流程结构。如果您的网站没有使用工作流程，使用和英语文化，或者没有安装本地化软件包，那么它不会受到影响。

Warning on Email Workflows Activities

电子邮件工作流程活动警告

If you use the Send Email activity in Workflows to send emails you may want to check whether you have the Email Workflows Activities feature enabled. Due to a bug you could use the Send Email activity even if you had the feature disabled, but this was fixed and now you have to enable Email Workflows Activities to be able to send emails.

如果您使用“工作流程”中的“发送电子邮件”活动发送电子邮件，则可能需要检查是否启用了“电子邮件工作流程活动”功能。由于存在错误，即使您已禁用该功能，也可以使用“发送电子邮件”活动，但这已修复，现在您必须启用“电子邮件工作流程活动”才能发送电子邮件。

Warning on Dynamic Forms feature relocation

动态表单功能重定位警告

There are two new features in the Dynamic Forms module, Dynamic Forms Validation Activities and Dynamic Forms User Bindings. These contain the C# form submission validator and bindings for UserPart, respectively. Since these were moved to their own features from the root feature (to avoid the root feature depend on the Orchard.Scripting.CSharp and Orchard.Users modules) if you make use of these services you have to enable the new features.

动态表单模块中有两个新功能，动态表单验证活动和动态表单用户绑定。它们分别包含C＃表单提交验证器和“UserPart”的绑定。由于这些功能是从根功能转移到自己的功能（以避免根功能依赖于Orchard.Scripting.CSharp和Orchard.Users模块），如果您使用这些服务，则必须启用新功能。

.NET 4.5.2 breaks module compilation

.NET 4.5.2打破了模块编译

Because the Orchard.Framework project now targets .NET 4.5.2, all modules that are downloaded from the gallery during development will need to be retargetd to .NET 4.5.2 too.

由于Orchard.Framework项目现在以.NET 4.5.2为目标，因此在开发过程中从库中下载的所有模块也需要重新定位到.NET 4.5.2。

Not doing this will prevent the module from compiling and appearing in the modules list.

不这样做会阻止模块编译并出现在模块列表中。

Contributors

贡献者

This software would not exist without the community. In particular, for this release,

没有社区，该软件将不存在。特别是，对于此版本，

we should all be grateful to the following people who contributed patches and features:

我们都应该感谢以下提供补丁和功能的人：

  • Alex Petryakov (neTp9c)

  • Alex Petryakov（[neTp9c]（https://github.com/neTp9c））

  • Alexey Ryazhskikh (musukvl)

  • Alexey Ryazhskikh（[musukvl]（https://github.com/musukvl））

  • Arman Forghani (armanforghani)

  • Arman Forghani（[armanforghani]（https://github.com/armanforghani））

  • Baruch Nissenbaum (qt1)

  • Baruch Nissenbaum（[qt1]（https://github.com/qt1））

  • Benedek Farkas (Lombiq)

  • Benedek Farkas（[Lombiq]（https://github.com/Lombiq））

  • Bertrand Le Roy (bleroy)

  • Bertrand Le Roy（[bleroy]（https://github.com/bleroy））

  • Chris Payne (paynecrl97)

  • 克里斯佩恩（[paynecrl97]（https://github.com/paynecrl97））

  • Connor Smallman (connorsmallman)

  • Connor Smallman（[connorsmallman]（https://github.com/connorsmallman））

  • Daniel Lackenby (DanielLackenbyBede)

  • Daniel Lackenby（[DanielLackenbyBede]（https://github.com/DanielLackenbyBede））

  • Daniel Stolt (DanielStolt)

  • Daniel Stolt（[DanielStolt]（https://github.com/DanielStolt））

  • Gustavo Tandeciarz (dcinzona)

  • Gustavo Tandeciarz（[dcinzona]（https://github.com/dcinzona））

  • Hannan Azam (hannan-azam)

  • Hannan Azam（[hannan-azam]（https://github.com/hannan-azam））

  • Jamie Philips (phillipsjs)

  • 杰米飞利浦（[phillipsjs]（https://github.com/phillipsjs））

  • Jean-Thierry Kéchichian (jtkech)

  • Jean-ThierryKéchichian（[jtkech]（https://github.com/jtkech））

  • Jerome van den Heuvel (Jwheuvel)

  • Jerome van den Heuvel（[Jwheuvel]（https://github.com/Jwheuvel））

  • Katsuyuki Ohmuro (harmony7)

  • Katsuyuki Ohmuro（[harmony7]（https://github.com/harmony7））

  • Kexy Biscuit (KexyBiscuit)

  • Kexy Biscuit（[KexyBiscuit]（https://github.com/KexyBiscuit））

  • Levent Esen (leventesen)

  • Levent Esen（[leventesen]（https://github.com/leventesen））

  • Marek Dzikiewicz (MpDzik)

  • Marek Dzikiewicz（[MpDzik]（https://github.com/MpDzik））

  • Matthew Harris (rtpHarry)

  • 马修哈里斯（[rtpHarry]（https://github.com/rtpHarry））

  • Matt Varblow (mvarblow)

  • Matt Varblow（[mvarblow]（https://github.com/mvarblow））

  • Mohammed Kinawy (mkinawy)

  • Mohammed Kinawy（[mkinawy]（https://github.com/mkinawy））

  • Nicholas Mayne (Jetski5822)

  • 尼古拉斯·梅恩（[Jetski5822]（https://github.com/Jetski5822））

  • Paul Devenney (PaulDevenney)

  • Paul Devenney（[PaulDevenney]（https://github.com/PaulDevenney））

  • Piotr Szmyd (pszmyd)

  • Piotr Szmyd（[pszmyd]（https://github.com/pszmyd））

  • Rob King (gcsuk)

  • Rob King（[gcsuk]（https://github.com/gcsuk））

  • Ryan Drew Burnett (ryandrewburnett)

  • Ryan Drew Burnett（[ryandrewburnett]（https://github.com/ryandrewburnett））

  • Sebastien Ros (sebastienros)

  • Sebastien Ros（[sebastienros]（https://github.com/sebastienros））

  • Sipke Schoorstra (sfmskywalker)

  • Sipke Schoorstra（[sfmskywalker]（https://github.com/sfmskywalker））

  • Szymon Seliga (SzymonSel)

  • Szymon Seliga（[SzymonSel]（https://github.com/SzymonSel））

  • Thierry Fleury (TFleury)

  • Thierry Fleury（[TFleury]（https://github.com/TFleury））

  • Titus Anderson (flew2bits)

  • 泰特斯安德森（[flew2bits]（https://github.com/flew2bits））

  • Westley Harris (wharri220)

  • 韦斯特利哈里斯（[wharri220]（https://github.com/wharri220））

  • Zhi Sun (sunz7)

  • Zhi Sun（[sunz7]（https://github.com/sunz7））

  • Zoltán Lehóczky (Lombiq)

  • ZoltánLehóczky（[Lombiq]（https://github.com/Lombiq））