考虑到 eZ Publish 的所有优点，您应该意识到它的缺点。从程序员的角度来看：系统大部分是用php4编写的，并且匆忙重写，以使其能够与php5兼容。内核中缺乏设计模式和面向对象的方法，使得系统难以开发和阅读其代码。要添加 CMS 未提供的一些较重的功能，您可以使用扩展系统。问题是扩展编程既缓慢又痛苦（文档仅以代码形式呈现）。 www.ez.no 上有相当好的技术文档，但其中大部分是针对网页设计师的。
Having in mind all good points of eZ Publish you should be aware of bad ones. From programmer point of view: Most of the system was written in php4, and was rewritten in a hurry, to make it works with php5. Lack of design patterns and object oriented approach in kernel, makes system hard to develope with, and to read its code. To add some heavier functionality not supplied by CMS, you can use extension system. Problem is programming extensions is slow and painful (documentation only in code). There is quite good technical documentation on www.ez.no but most of it is for webdesigners.
I'v used ezPublish for quite a while and I can say its very flexible and allows a range of different solutions to quickly be developed with it. The ability to add content types is what makes it awesome.
It can be a little bit slow at times, but with proper caching set up it can also be really fast.
我想说，如果您长期从事该行业并且有能力培训您的开发人员（实际上，您不能不这样做），那么 eZ Publish 是一个相当不错的选择。一旦您找到了平台并开发了自己的工具包，部署自定义解决方案应该相当快。
我也同意之前的答案，即班级制度确实很出色。缓存始终是一个问题，所以不要忘记学习缓存系统。您的网站可以在 eZ Publish 上运行，但您必须了解缓存才能实现这一点！
The biggest downside: The learning curve is very steep and long, and there aren't enough knowledgeable eZ Publish developers available in North America.
However, from the beginning I've been fond of its overall architecture, which seems to be elegant, flexible and generally well thought-out. Over time, some things have been bolted on in ways that don't necessarily fit perfectly. But it's pretty amazing what you can accomplish with the core functionality, and overriding and extending the core is clean and maintains good separation.
I would say that if you are in it for the long haul and can afford to train your developers (really, you can't afford not to) then eZ Publish is a reasonably good choice. Once you figure out the platform and develop your own kit of tools, it should be fairly quick to deploy custom solutions.
I will also concur with an earlier answer, that the class system really shines. Caching is always an issue, so don't forget to learn the caching system. Your site can fly on eZ Publish, but you must understand caching to make it do so!
我已经使用 eZ Publish 好几年了。 一开始学习它并理解其结构是相当困难的，但是当你上路时，一切都会变得简单而快速，特别是在 Symfony2 上使用他们的新内核。
I have Used eZ Publish for some years now. It was quite difficult to learn it at first and understanding the structure, but when you are on the way then everything would be simple and fast, especially with their new kernel on Symfony2.
I would recommend using eZPublish 5, as I suppose you no longer talk about the older versions, only if you have at least some basic knowledge of eZ version4. That is because the admin is still using the legacy and all the settings are done using .ini files which you really have to know. Nothing hard, but learning curve is definitely steep.
Also using eZFlow will require working with both .ini and .yml configuration files, so you need to understand both config structures.
Further on, as I have been at a presentation for the new admin, which unfortunately will be using YUI as JS framework, and having seen the release plan for this year, I can say you will have to keep the legacy admin if you want to benefit of all the functionalities as there is an enormous amount of work to be done to have everything migrated on Symfony 2.
Even with the announcement of eZPlatform(eZ 6), I am not that confident we will have a really STABLE version anywhere this year.
发布评论
评论（5）
考虑到 eZ Publish 的所有优点，您应该意识到它的缺点。从程序员的角度来看：系统大部分是用php4编写的，并且匆忙重写，以使其能够与php5兼容。内核中缺乏设计模式和面向对象的方法，使得系统难以开发和阅读其代码。要添加 CMS 未提供的一些较重的功能，您可以使用扩展系统。问题是扩展编程既缓慢又痛苦（文档仅以代码形式呈现）。 www.ez.no 上有相当好的技术文档，但其中大部分是针对网页设计师的。
Having in mind all good points of eZ Publish you should be aware of bad ones. From programmer point of view: Most of the system was written in php4, and was rewritten in a hurry, to make it works with php5. Lack of design patterns and object oriented approach in kernel, makes system hard to develope with, and to read its code. To add some heavier functionality not supplied by CMS, you can use extension system. Problem is programming extensions is slow and painful (documentation only in code). There is quite good technical documentation on www.ez.no but most of it is for webdesigners.
我使用 ezPublish 已经有一段时间了，我可以说它非常灵活，并且允许使用它快速开发一系列不同的解决方案。添加内容类型的能力使其变得很棒。
有时它可能会有点慢，但是通过适当的缓存设置，它也可以非常快。
I'v used ezPublish for quite a while and I can say its very flexible and allows a range of different solutions to quickly be developed with it. The ability to add content types is what makes it awesome.
It can be a little bit slow at times, but with proper caching set up it can also be really fast.
最大的缺点：学习曲线非常陡峭且漫长，而且北美没有足够的知识渊博的 eZ Publish 开发人员。
然而，从一开始我就很喜欢它的整体架构，它看起来优雅、灵活，而且总体上是经过深思熟虑的。随着时间的推移，有些东西的固定方式不一定完全合适。但使用核心功能可以完成的事情是非常令人惊奇的，并且重写和扩展核心是干净的并且保持良好的分离。
我想说，如果您长期从事该行业并且有能力培训您的开发人员（实际上，您不能不这样做），那么 eZ Publish 是一个相当不错的选择。一旦您找到了平台并开发了自己的工具包，部署自定义解决方案应该相当快。
我也同意之前的答案，即班级制度确实很出色。缓存始终是一个问题，所以不要忘记学习缓存系统。您的网站可以在 eZ Publish 上运行，但您必须了解缓存才能实现这一点！
The biggest downside: The learning curve is very steep and long, and there aren't enough knowledgeable eZ Publish developers available in North America.
However, from the beginning I've been fond of its overall architecture, which seems to be elegant, flexible and generally well thought-out. Over time, some things have been bolted on in ways that don't necessarily fit perfectly. But it's pretty amazing what you can accomplish with the core functionality, and overriding and extending the core is clean and maintains good separation.
I would say that if you are in it for the long haul and can afford to train your developers (really, you can't afford not to) then eZ Publish is a reasonably good choice. Once you figure out the platform and develop your own kit of tools, it should be fairly quick to deploy custom solutions.
I will also concur with an earlier answer, that the class system really shines. Caching is always an issue, so don't forget to learn the caching system. Your site can fly on eZ Publish, but you must understand caching to make it do so!
我已经使用 eZ Publish 好几年了。
一开始学习它并理解其结构是相当困难的，但是当你上路时，一切都会变得简单而快速，特别是在 Symfony2 上使用他们的新内核。
I have Used eZ Publish for some years now.
It was quite difficult to learn it at first and understanding the structure, but when you are on the way then everything would be simple and fast, especially with their new kernel on Symfony2.
我建议使用 eZPublish 5，因为我想您不再谈论旧版本，除非您至少对 eZ version4 有一些基本了解。这是因为管理员仍在使用旧版本，并且所有设置都是使用您确实必须知道的 .ini 文件完成的。没什么难的，但学习曲线绝对是陡峭的。
此外，使用 eZFlow 需要同时使用 .ini 和 .yml 配置文件，因此您需要了解这两种配置结构。
此外，由于我参加了新管理员的演示，不幸的是，新管理员将使用 YUI 作为 JS 框架，并且看到了今年的发布计划，我可以说，如果您想，您将必须保留旧版管理员受益于所有功能，因为要将所有内容迁移到 Symfony 2 上需要做大量的工作。
即使宣布了 eZPlatform(eZ 6)，我也不太有信心今年我们将在任何地方拥有一个真正稳定的版本。
I would recommend using eZPublish 5, as I suppose you no longer talk about the older versions, only if you have at least some basic knowledge of eZ version4. That is because the admin is still using the legacy and all the settings are done using .ini files which you really have to know. Nothing hard, but learning curve is definitely steep.
Also using eZFlow will require working with both .ini and .yml configuration files, so you need to understand both config structures.
Further on, as I have been at a presentation for the new admin, which unfortunately will be using YUI as JS framework, and having seen the release plan for this year, I can say you will have to keep the legacy admin if you want to benefit of all the functionalities as there is an enormous amount of work to be done to have everything migrated on Symfony 2.
Even with the announcement of eZPlatform(eZ 6), I am not that confident we will have a really STABLE version anywhere this year.