Skip to content

Orchard 1.8

建立：1.8

Published: 03/28/2014

发布时间：03/28/2014

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.8.zip file.

或者，要手动安装发行版，请下载Orchard.Web.1.8.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.1.8.zip

如果你只是想使用Orchard而不关心源代码，Orchard.Web.1.8.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.Source.1.8.zip is fine.

Orchard.Source.1.8.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.8. The code is in a stable state and constitutes

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

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.8 fixes bugs and introduces the following changes and features:

Orchard 1.8修复了错误并引入了以下更改和功能：

  • Migration to Microsoft .NET 4.5

  • 迁移到Microsoft .NET 4.5 *

  • Upgrade project targets

  • 升级项目目标 *

  • Remove unnecessary Medium Trust support code

  • 删除不必要的Medium Trust支持代码 *

  • Define 4.5 framework in web.config files

  • 在web.config文件中定义4.5框架 *

  • Erik (erik_oppedijk) owns this contribution

  • Erik（[erik_oppedijk]（https://www.codeplex.com/site/users/view/erik_oppedijk））拥有此贡献 *

  • Upgrade ASP.NET Web Stack to newest versions

  • 将ASP.NET Web Stack升级到最新版本 *

  • ASP.NET MVC 5.1

  • ASP.NET MVC 5.1 *

  • WebAPI 2.1

  • WebAPI 2.1 *

  • Razor 3.1

  • 剃刀3.1 *

  • Put back the List module with improved functionalities

  • 使用改进的功能放回List模块 *

  • The goal is to be able to use it to mimick the Blogs module

  • 目标是能够使用它来模仿博客模块 *

  • Sipke (sfmskywalker) owns this contribution

  • Sipke（[sfmskywalker]（http://www.codeplex.com/site/users/view/sfmskywalker））拥有此贡献 *

  • Performance improvements by unleashing the power of the document db architecture built in Orchard

  • 通过释放Orchard中构建的文档数据库体系结构的强大功能来提高性能 *

  • Sebastien (sebastienros) owns this contribution

  • Sebastien（[sebastienros]（http://www.codeplex.com/site/users/view/sebastienros））拥有此贡献 *

  • Multi-tenancy improvements

  • 多租户改进 *

  • Calendar support

  • 日历支持 *

  • Daniel Stolt (Decorum) owns this contribution

  • Daniel Stolt（[Decorum]（https://www.codeplex.com/site/users/view/Decorum））拥有此贡献 *

  • Jobs Queue module (done)

  • 作业队列模块（完成） *

  • Orchard.JobsQueueing

  • Orchard.JobsQueueing *

  • Templates module (done)

  • 模板模块（完成） *

  • Orchard.Templates

  • Orchard.Templates *

  • Business Caching modules

  • 业务缓存模块 *

  • Orchard.Caching

  • Orchard.Caching *

  • Orchard.Email

  • Orchard.Email *

  • The messaging infrastructure has been deprecated and replaced by a simpler one. As part of this change you can now define the email templates directly in shapes.

  • 消息传递基础结构已被弃用，并由更简单的基础结构取代。作为此更改的一部分，您现在可以直接在形状中定义电子邮件模板。 *

  • The SMTP settings are read from the web.config file by default if available.

  • 默认情况下，如果可用，则从web.config文件中读取SMTP设置。 *

  • Azure Media Services has been contributed by Microsoft Open Technologies and provides a seamless integration with the Media module

  • Azure Media Services由Microsoft Open Technologies提供，并提供与媒体模块的无缝集成 *

  • Orchard.Azure.MediaServices

  • Orchard.Azure.MediaServices *

  • Orchard.Azure:

  • Orchard.Azure： *

    • PlatformConfiguration (static class to read settings from CloudConfigurationManager) is gone. Its place is taken by an injectable dependency called IPlatformConfigurationAccessor and the old implementation's logic is moved to the DefaultPlatformConfigurationAccessor class, which was then extended to look for settings among the ConnectionStrings too.

    • These changes are reflected throughout the Orchard.Azure module, though the Azure database cache's behavior (AzureCache* classes) is not affected by IPlatformConfigurationAccessor implementations other than DefaultPlatformConfigurationAccessor due to certain NHibernate limitations.

    • Added a new setting called Orchard.Azure.Media.StoragePublicHostName which makes it possible to override the public host name when using Azure storage.

    • Orchard.Azure.Media and Orchard.Azure.DatabaseCache now depend on Orchard.Azure.

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

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

  • Bugs fixed in 1.8.

  • [错误修复于1.8]（https://orchard.codeplex.com/workitem/list/advanced?keyword=\u0026status=Resolved%7CClosed\u0026type=All\u0026priority=All\u0026release=Orchard%201.8\u0026assignedTo=All\u0026component=All\u0026sortField=LastUpdatedDate\u0026sortDirection=Scendingnding@page=reasonClosed=所有）。 *

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.7.1 and earlier

从Orchard 1.7.1及更早版本升级

Please follow the upgrade instruction from this document: https://github.com/OrchardCMS/OrchardDoc/blob/1.8/Documentation/Orchard-1-7-2-Release-Notes.markdown

请按照本文档中的升级说明进行操作：https://github.com/OrchardCMS/OrchardDoc/blob/1.8/Documentation/Orchard-1-7-2-Release-Notes.markdown

Then proceed with the upgrade steps from 1.7.2.

然后继续执行1.7.2中的升级步骤。

Upgrading from Orchard 1.7.2

从Orchard升级1.7.2

BEFORE DOING ANYTHING PLEASE FOLLOW THIS STEPS:

在执行任何操作之前，请按照以下步骤操作：

  • Backup your database and your website content

  • 备份数据库和网站内容 *

  • Assign the Administrator role to your current Super User account.

  • __将“管理员”角色分配给您当前的超级用户帐户___。 *

You will need an account with the Site Owner permission before you update your website with the new release. Without this step you won't be able to access the dashboard.

在使用新版本更新网站之前，您将需要具有“站点所有者”权限的帐户。如果没有此步骤，您将无法访问仪表板。

In case you are discovering this notice too late, here is the manual operation to apply. In your database table Orchard_Framework_ContentItemRecord, on the record with id=1 (the site content item), update the value with this content <Data><SiteSettingsPart SuperUser="admin"/></Data>

如果您发现此通知为时已晚，请执行以下手动操作。在您的数据库表Orchard_Framework_ContentItemRecord中，在具有id = 1（站点内容项）的记录上，使用此内容更新值<Data> <SiteSettingsPart SuperUser =“admin”/> </ Data>

  • Enable the Upgrade module

  • 启用升级模块 *

Migrating Email activities

迁移电子邮件活动

In Orchard 1.8 the Send Email workflow activity has been replaced by a new one which is able to send emails asynchronously using the Jobs Queue.

在Orchard 1.8中，发送电子邮件工作流活动已被新的替换，该活动能够使用作业队列异步发送电子邮件。

  • Click on Upgrade To 1.8 from the menu

  • 单击菜单中的Upgrade To 1.8 *

  • Select the Messaging tab and click Migrate

  • 选择Messaging选项卡，然后单击 Migrate

Migrating Infoset

迁移信息集

In Orchard 1.8 a new data storage technique is introduced saving some of the content in the infoset document of content items instead of records. This way some records are obsolete and can be deleted. The data it contained needs to be migrated though.

在Orchard 1.8中，引入了一种新的数据存储技术，在内容项的信息集文档中保存了一些内容而不是记录。这样一些记录已经过时，可以删除。它包含的数据需要迁移。

  • Click on Upgrade To 1.8 from the menu

  • 单击菜单中的Upgrade To 1.8 *

  • Select the Infoset tab and click on all the Migrate buttons one at a time

  • 选择Infoset选项卡，然后一次单击所有 Migrate 按钮

If you are not sure if one button was clicked you can try again and it will just be ignored if it was already processed.

如果您不确定是否单击了一个按钮，则可以再次尝试，如果已经处理，则会被忽略。

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:

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

  • Antoine Griffard (agriffard)

  • Antoine Griffard（[agriffard]（http://www.codeplex.com/site/users/view/agriffard））

  • Anthony R. Fassett (fassetar)

  • Anthony R. Fassett（[fassetar]（https://www.codeplex.com/site/users/view/fassetar））

  • Benedek Farkas (nightwolf226)

  • Benedek Farkas（[nightwolf226]（https://www.codeplex.com/site/users/view/nightwolf226））

  • Benjamin Grabkowitz (bgrabkowitz)

  • Benjamin Grabkowitz（[bgrabkowitz]（https://www.codeplex.com/site/users/view/bgrabkowitz））

  • Bertrand Le Roy (bertrandleroy)

  • Bertrand Le Roy（[bertrandleroy]（http://www.codeplex.com/site/users/view/bertrandleroy））

  • Brett Morrison (morrisonbrett)

  • Brett Morrison（[morrisonbrett]（https://www.codeplex.com/site/users/view/morrisonbrett））

  • Claire Botman (planetClaire)

  • Claire Botman（[planetClaire]（https://www.codeplex.com/site/users/view/planetClaire））

  • Daniel Dabrowski (rodpl)

  • Daniel Dabrowski（[rodpl]（https://www.codeplex.com/site/users/view/rodpl））

  • Daniel Stolt (Decorum)

  • Daniel Stolt（[Decorum]（https://www.codeplex.com/site/users/view/Decorum））

  • Erik Oppedijk (erik_oppedijk)

  • Erik Oppedijk（[erik_oppedijk]（https://www.codeplex.com/site/users/view/erik_oppedijk））

  • Eric Schultz (wwahammy)

  • Eric Sc​​hultz（[wwahammy]（https://www.codeplex.com/site/users/view/wwahammy））

  • Gilian Keulens (Walance)

  • Gilian Keulens（[Walance]（http://www.codeplex.com/site/users/view/Walance））

  • Henry Kuijpers (hkui)

  • Henry Kuijpers（[hkui]（https://www.codeplex.com/site/users/view/hkui））

  • Jay Harris (jayharris)

  • 杰伊哈里斯（[jayharris]（https://www.codeplex.com/site/users/view/jayharris））

  • Jasper Dunker (jasperd)

  • Jasper Dunker（[jasperd]（http://www.codeplex.com/site/users/view/jasperd））

  • Jean-Thierry Kéchichian (jtkech)

  • Jean-ThierryKéchichian（[jtkech]（https://www.codeplex.com/site/users/view/jtkech））

  • Jeff Olmstead (jao28)

  • Jeff Olmstead（[jao28]（https://www.codeplex.com/site/users/view/jao28））

  • Jim Macdonald (Jimasp)

  • Jim Macdonald（[Jimasp]（http://www.codeplex.com/site/users/view/Jimasp））

  • Josh Berry (joshby)

  • Josh Berry（[joshby]（https://www.codeplex.com/site/users/view/joshby））

  • kassobasi (kassobasi)

  • kassobasi（[kassobasi]（https://www.codeplex.com/site/users/view/kassobasi））

  • Michael Yates (mjy78)

  • Michael Yates（[mjy78]（http://www.codeplex.com/site/users/view/mjy78））

  • Piotr Szmyd (pszmyd)

  • Piotr Szmyd（[pszmyd]（https://www.codeplex.com/site/users/view/pszmyd））

  • Sebastien Ros (sebastienros)

  • Sebastien Ros（[sebastienros]（http://www.codeplex.com/site/users/view/sebastienros））

  • Sipke Schoorstra (sfmskywalker)

  • Sipke Schoorstra（[sfmskywalker]（http://www.codeplex.com/site/users/view/sfmskywalker））

  • Stanley Goldman (StanleyGoldman)

  • Stanley Goldman（[StanleyGoldman]（http://www.codeplex.com/site/users/view/StanleyGoldman））

  • Thierry Fleury (Codinlab)

  • Thierry Fleury（[Codinlab]（https://www.codeplex.com/site/users/view/Codinlab））

  • Tony Mackay (toneuk)

  • Tony Mackay（[toneuk]（https://www.codeplex.com/site/users/view/toneuk））

  • Yury Arzhevikin (Gorizon47)

  • Yury Arzhevikin（[Gorizo​​n47]（http://www.codeplex.com/site/users/view/Gorizo​​n47））

  • Zoltán Lehóczky (Piedone)

  • ZoltánLehóczky（[Piedone]（http://www.codeplex.com/site/users/view/Piedone））

Special Thanks to Christian Surieux (csadnt) for his active participation on the forums.

特别感谢Christian Surieux（[csadnt]（http://www.codeplex.com/site/users/view/csadnt））积极参与论坛。