We are pleased to announce the first stable releases of eZ Publish 4.0.0 and eZ Flow 1.0. These releases add considerable value to eZ Publish and benefit the entire eZ Ecosystem. eZ Publish 4 signifies our commitment to provide a sustainable platform for delivering Enterprise Content Management Solutions, while eZ Flow enables media companies to engage visitors with rich, dynamic multimedia content, providing an easy-to-use interface for non-technical editors.
In addition to eZ Publish, the eZ Flow extension provides the following capabilities and functionality, mainly targeted at news and media organizations:
This extension is included as an optional install in the eZ Publish 4.0 distribution
For eZ Publish and eZ Flow in particular, we invite you to have a look at our new video presentation
Before you install or run extensions other than those provided with eZ Publish 4.0.0, you must install eZ Components. (In the future we will bundled eZ Components with eZ Publish for your convenience). Refer to the documentation for instructions on installing eZ Components using PEAR.
The recommended version of PHP-5 is the latest stable release (PHP5.2.5 as of this writing). PHP5.1 is currently also supported.
The date.timezone directive must be set in php.ini or in .htaccess. For a list of supported timezones please see http://php.net/manual/en/timezones.php
You can use Apache 1.3 or Apache 2.x in pre-forking mode. For Windows, Apache 1.3 is the only recommended option.
All eZ Publish versions in this family require Unicode enabled in the database. For MySQL, this means the minimum version is MySQL 4.1. The latest stable version is recommended. Please note that support for Oracle is planned, but not available yet.
In eZ Publish 4 we use the PHP-5 autoload feature to load classes. This means
that when new classes are introduced to the system, the autoload arrays need
to be updated.
There are several situations when a user might want to regenerate the
autoload-arrays:
Two methods are provided: a command-line version and through the Administration Interface. For more information, consult the documentation (which will be updated soon).
In eZ Publish 4, the default URL alias setting is 'urlalias', meaning that URLs will be created with mostly ASCII characters. The case of the text will be preserved, and dashes (and other characters) are available as a word separator. However, other settings are available, such as 'urlalias_iri', which is the same as above but which will also include unicode characters in the URLs (this was the default in the 4.0 alpha, beta and rc releases).
In eZ Publish 4 certain features have been deprecated. These will gradually be removed in a future release, when we have better replacements ready.
The following datatypes are deprecated:
The following views have been deprecated:
The follow kernel libraries have been deprecated:
You can download the archives of eZ Publish 4.0.0 (which includes eZ Flow as an option during installation) here
The full changelogs are available too
Comments
re: Upgrade information
Svitlana Shatokhina
2007年 12月 11日 火曜日 17:48:11
Direct upgrade from 3.9 to 4.0 is not possible, you will need to upgrade to 3.10 first, see http://issues.ez.no/12186
re: Upgrade information
André R.
2007年 12月 9日 日曜日 19:49:49
Upgrade information
Leif Arne Storset
2007年 12月 9日 日曜日 18:50:18
re: Apache
André R.
2007年 12月 5日 水曜日 11:00:57
Short: Apache 2.x has several Modules, the default is Multi-Threaded Module and is not recommended for php at all! prefork is short for Multi-Processing Module, and is similar to how Apache 1.3 works.
Windows: We could not find any binary versions of Apache 2.x prefork, that's why we recommend Apache 1.3.39 for the time being.
Apache
Erich Strasser
2007年 12月 5日 水曜日 10:49:07
What means pre-forking mode?
Digg it!
Heath
2007年 12月 4日 火曜日 02:27:49
Some Additional Notes:
André R.
2007年 12月 4日 火曜日 00:50:26
you can no longer include template files from the override directory directly, templates there are for overrides only.
* All/most constants are moved to a suitable class, so make sure you clean your own datatypes / extensions when you upgrade them.
* Static class functions are now marked as static and some clean up where necessary on class functions that worked both as static and as member.
* Class functions that had names like 'remove' or 'clone' where renamed to comply with php 5 naming rules.