Book Image

eZ Publish 4: Enterprise Web Sites Step-by-Step

Book Image

eZ Publish 4: Enterprise Web Sites Step-by-Step

Overview of this book

eZ Publish provides developers with a structure to build highly impressive applications and then quickly deploy them into a live environment. eZ Publish is complex, with a steep learning curve, but with the right direction it offers great flexibility and power. What makes eZ Publish special is not the long list of features, but what's going on behind the scenes. Created specifically for newcomers to eZ Publish, and using an example Magazine web site, this book focuses on designing, building and deploying eZ Publish to create an enterprise site quickly and easily. This tutorial takes eZ Publish's steep learning curve head-on, and walks you through the process of designing and building content-rich web sites. It makes the unrivalled power and flexibility of eZ Publish accessible to all developers. The book is organized around technical topics, which are handled in depth, with a general progression that follows the learning experience of the reader, and features a single magazine web site project from installation to completion and deployment. This hands-on guide helps the reader to understand the Content Management System to create a web 2.0-ready web site by creating new extensions or overriding the existing ones. In turn, it helps you to become confident when working in the eZ Publish administration area and offers an environment in which you can practice while working through the chapters.
Table of Contents (20 chapters)
eZ Publish 4: Enterprise Web Sites Step-by-Step
Credits
About the Authors
About the Reviewer
Preface
Advance Debugging

Default caching settings


In the default configuration, all of the major levels of caching are enabled. If you install a "white label" eZ Publish, the only level not enabled by default is the Smart Cache, which needs to be configured manually, as seen in the previous section.

When we develop our project, it is very inconvenient to have the ContentCache setting enabled. This is because it means that we have to delete it every time we want to see the changes that we applied to a template.

To solve this problem, you can enable the DevelopmentMode setting in the TemplateSettings section of the global (or override) site.ini file that performs many more checks on the cancellation time of a template. But that directive is effective only on the content's cache, and not on the layout cache block.

If you want to disable the cache in an absolute way, you must add the following configuration settings to the global (or siteaccess) site.ini.append.php file:

[ContentSettings]
ViewCaching=disabled
[TemplateSettings...