主頁 > 新聞 > 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