主页 > 新闻 > eZ Publish 4.1.0 正式发布

eZ Publish 4.1.0 正式发布

众所瞩目的eZ Publish 4.1.0现在正式发布,这个版本包含了许多新的内建功能以及相关的扩充套件,程式除错与补强,和网站效能的提升。

 

eZ Publish 4.1 新增的功能

核心功能

Object States

Object States让既有的排程系统(workflow)更富有弹性。假设您将编辑的物件纳入排程,您将无法继续编辑物件或更改物件的状态直到排成系统被赋与的 指令操作完成。 Object States允许您变更和继续编辑已加入排程系统中的物件。举个简单的例子:假设一个记者撰写好一篇新闻稿然后送交排程系统让指定的校阅者复查,如果校阅 者发现错字的话可以订正,最后再经由排程系统送到总编做最后的审核。以上作业因为有适当的角色和权限设定、Object States的辅助再加上排程的功能,不同的使用者或群组可以依照被赋与的角色分工合作完成同一件内容物却又不致于在工作流程上产生冲突。

 

支援 OpenSolaris 10

 

从eZ Publish 4.1起我们将正式支援OpenSolaris x86的作业平台。特别是结合Sun的AMP Stack ( Sun GlassFish Web Stack)之后,OpenSolaries提供eZ Publish使用者一个优秀的开发平台,增加了一个替代Linux或是Windows作业平台的选择。

 

改进Cache机制,提升网站整体效能

 

有些网站资料在第一次被查询过后系统就会自动产生cache以便之后的拜访者可以快速地取得相同的资料。而当这份资料被更新并且又有一个用户搜寻此资料, 一个新的cache就会相对应地产生。但有时候使用者所查询的资料刚好正在被更新中,因此会经历一小段等待新的cache产生的时间;同时如果刚好有许多 其他的使用者正在搜寻同一笔资料时,他们也必须等待新的cache出现。这对用户的网站使用经验以及网站整体的运行效能都是一种伤害。因此在新版的eZ Publish中提供了一个新的机制,当使用者搜寻的资料正好是系统需要汰旧换新的cache,系统会先提供即将被取代的(旧的) cache填补使用者的等待时间,而新的cache完成后将会自动替代旧的cache。如此一来可以减轻系统的负担,减少database deadlock的机会,同时也减少网站拜访者等待网页更新完全的时间,增加正面的网站使用经验。

 

其他核心功能补强

 

  • Introduction of low level eZ Components (Archive handler, System information, WebDAV, ConsoleTools),
  • A new language switcher
  • Improved WebDAV handler
  • Provisions for more handler methods for eZ Find and other search plugins, ....
  • New operations and triggers have been added
  • Template override, object and node fetch by remote id
  • New settings for improved flexibility and debug tracing in LDAP (ref: #12114)
  • Improved session security by regenerating session id on log in/log out and configurable validation of session (ref: #14264)
  • Added settings for tweaking view cache efficiency (ref: #14344)
  • Missing connection to database, will now throw an exception, and stop the loading of the page

 

新增的扩充套件

eZ OE 5.0 (自动安裝)

 

eZ Online Editor 5.0取代了原有的Online Editor 4.x并且使用了不同的编辑器:TinyMCE。 eZ OE 5.0支援IE 7 Vista、全萤幕编辑模式、弹性调整撰写区域的大小,以及提供更多的内建功能。

 

eZ Flow 1.1 (安裝时可选)

 

新版的eZ Flow提供更多编辑相关的功能,支援iPhone,以及强化多媒体支援的功能。

 

eZ Webin 1.4 (安裝时可选)

 

新的eZ Webin包含了许多的程式补强、既有功能面的提升、以及增加了一些新的功能,像是您可以更灵活地切割您的pagelayout让网页设计与客制化更容易;另外有些与accessibility相关的功能也在此版本加入。

 

Multi-file upload 1.0

 

eZ Multiupload让使用者轻松上传多个档案一次完成。您可以选择藉由eZ Publish前台直接上传档案,像是图片、文件、影音档等等。结合eZODF (eZ Open Document Format)扩充套件的应用,您可先在OpenDocument Text或是Miscrosoft Word撰写好多篇文章,然后再直接一起上传到您的eZ Publish网站。

 

相关技术细节请参考: http://projects.ez.no/ezmultiupload

 

eZ Oracle 2.0

 

eZ Oracle让您也可以使用Oracle作为eZ Publish的资料库伺服器(database server)。

 

相关技术细节请参考: http://projects.ez.no/ezoracle

 

eZ MB Password expiry extension 1.0

 

ezmbpaex可让您自己定义密码的有效期限。一旦密码过期时,这个扩充套件就会要求使用者再给予一个新的密码。这个功能时常被用于intranets与extranets。

 

相关技术细节请参考: http://projects.ez.no/mbpaex

 

中文版技术手冊

 

前针对eZ Publish 4.x的中文技术手册可参考社群所提供的 eZ Publish 4 Technical Manual (Simplified Chinese)。其他与eZ Publish及其扩充套件相关的中文手册可在此找到 http://ez.no/developer/contribs/documentation

 

已知的潜在问題

 

  • PostgreSQL support is partly broken, and will be addressed in the next maintenance release
  • Cache issues that will be fixed in the next maintenance release (see http://issues.ez.no/14622 and http://issues.ez.no/14627 )
  • Oracle support does not include clustering yet
  • PEAR version of eZ Components is used even if you download the bundled version (so if you have PEAR version, make sure its version 2008.2 or higher)

 

升級 4.0.x 的系統到 4.1版本

 

Please use a copy before attempting to upgrade!

 

The update information is not completed yet, so a minimal set of instructions is included here. Detailed instructions will be provided with the next interim releases

 

0) Check the eZ Components 2008.2 requirements (added 2009-03-22)

 

With eZ Publish 4.1.0, eZ Components 2008.2 is the minimum version required. If you installed a previous version with PEAR, please upgrade to version 2008.2. For more information see also http://ezcomponents.org/docs/install

 

1) Updating the distribution files

 

The easiest way to upgrade the distribution files is to unpack eZ Publish 4.1.0 to a separate directory and then copy the directories that contain site-specific files from the existing installation. Make sure that you copy the following directories:

 

  • design/example
  • design/example_admin
  • var
  • settings/siteaccess
  • settings/override

 

Replace "example" and "example_admin" with the actual names of your siteaccesses.

 

2) Custom extensions

 

If you are using custom extensions, the subdirectories inside the "extension" directory will also have to be copied. However, make sure that you do not overwrite any extensions that come with eZ Publish (currently "ezoe", "ezodf"). Note that upgrading the distribution files will overwrite the autoload arrays for extensions. You will need to re-generate the autoload arrays for active extensions late.

 

See below for dedicated upgrade instructions for ez flow and ez webin.

 

Note that ezdhtml is now replaced by ezoe, so you should not copy it over.

 

For eZ OE 5.0, you will need to have the following rewrite rule if using Virtual Hosts:

RewriteRule ^/var/[^/]+/cache/public/.* - [L]

For more detailed instructions, see the dedicated doc page: http://ez.no/doc/extensions/online_editor/5_x/installation

 

3) Upgrading the database

 

The update script for the database is located in <root of ez publish installation>/update/database/<mysql|postgresql>/4.1/unstable/dbupdate-4.0.0-to-4.1.0.sql

 

You can run this with the appropriate command line tool or application

 

4) Regenerate the autoload array for extensions (added 2009-03-22)

 

The autoload system has also some changes, for example the autoload array for extensions is now placed in var/autoload of your eZ Publish installation (along teh class changes in extensions itself).

 

To regenerate the autoload array, execute the following script from

php bin/php/ezpgenerateautoloads.php --extension

5) Running the system upgrade scripts

 

The update scripts are located in <root of ez publish installation>/update/common/scripts/4.1

 

  • addlockstategroup.php (used for creating locked states, part of the object states functionality)
  • fixclassremoteid.php (fixing remote ids of classes)
  • fixezurlobjectlinks.php (to fix older occurrences of link items not being present in the ezurl_object_table for all versions/translations)
  • fixobjectremoteid.php (to fix non-unique usage of content object remote ID's)
  • initurlaliasmlid.php (Initialize the ezurlalias_ml_incr table, part of the fixed issue #14077: eZURLAliasML database table lock and unlock code causes implicit commit of database transaction)
  • updateimagesystem.php (optional: update all attributes with datatype ezimage to use the new image system introduced in eZ Publish 3.3 as older items may still exist)

 

升級 eZ Flow 或是 eZ Webin 版本

1) Backup

 

Before you will start the Website Interface or eZ Flow upgrading process make sure that you have backup of existing website state including database, extensions, INI settings, etc. During upgrade process existing ezflow and ezwebin extensions will be removed and replaced with new version. Website Interface and eZ Flow default content classes will be replaced as well. Upgrade script will also change some of the existing INI settings and add new ones which are required by latest version.

 

2) eZ Flow upgrade

 

eZ Publish 4.1 comes with eZ Flow upgrade script which allows upgrade from previous version to the latest 1.1-0 version. To run upgrade process in automatic mode simply execute following command from eZ Publish root folder.

php bin/php/ezflowupgrade.php --to-version=1.1-0 --url=http://packages.ez.no/ezpublish/4.1/4.1.0

It is very important that user which will execute the upgrade script had correct permissions to modify content user extension, settings and var folders.

 

In order to get more information about available upgrade options, execute ezflowupgrade.php script with –help param.

php bin/php/ezflowupgrade.php --help

3) Re-write rules

 

Users running their eZ Flow sites in VH mode should update their extension related re-write rules to the following:
Rewriterule ^/extension/[^/]+/design/[^/]+/(stylesheets|images|javascript|flash|lib?)/.* - [L]

 

4) Website Interface upgrade

 

Upgrading Website Interface is very similar to eZ Flow upgrade process. In order to upgrade existing installation to latest 1.4-0 version simply execute following command from eZ Publish root folder:

php bin/php/ezwebinupgrade.php --to-version=1.4-0 --url=http://packages.ez.no/ezpublish/4.1/4.1.0

Again, it is very important that user which will execute the upgrade script had correct permissions to modify content user extension, settings and var folders.
In order to get more information about available upgrade options, execute ezwebinupgrade.php script with –help param.

php bin/php/ezwebinupgrade.php --help

5) Regenerate the autoload array for extensions (added 2009-03-22)

 

The autoload system has also some changes, for example the autoload array for extensions is now placed in var/autoload of your eZ Publish installation (along teh class changes in extensions itself).

 

To regenerate the autoload array, execute the following script from

php bin/php/ezpgenerateautoloads.php --extension

6) Cache

 

Once the upgrade script is done, you need to clear the cache by executing following command from eZ Publish root folder:

php bin/php/ezcache.php --clear-all --purge

下载软件

 

The changelog is available here

 

eZ Publish 套件不含 eZ Components 2008.2

 

 

eZ Publish 套件包含 eZ Components 2008.2